System for issuing certificate based on blockchain network, and method for issuing certificate based on blockchain network by using same

ABSTRACT

A method for issuing certificates based on a blockchain network is provided. The method includes steps of: an authentication-supporting server, (a) if personal information on a user is acquired, (i) instructing a user device to generate a public and a private key of the user and transmit the public key to the authentication-supporting server, (ii) storing the certificate including the public hey as corresponding to the personal information, and (iii) determining whether one of current anchoring conditions is satisfied; (b) if it is, generating a root hash value by a Merkle tree operation on leaf nodes including hash values of the certificates stored after a previous anchoring condition is satisfied; and (c) one of (c-1) storing the transaction including the root hash value in a distributed database on the blockchain network and (c-2) instructing a blockchain node to store the transaction in the distributed database, and acquiring a transaction ID.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/008,359 filed on Jun. 14, 2018, which is a National Stage Entry of International Patent Application No. PCT/KR2016/011293, filed on Oct. 10, 2016, and claims priority to Korean Patent Application 10-2016-0038068, filed on Mar. 30, 2016, the entire contents of each of which being incorporated herein by reference,

FIELD OF THE INVENTION

The present disclosure relates to a method for issuing one or more certificates based on a blockchain network; and more particularly, to the method of, (a) if personal information on a specific user for issuing a specific certificate of the specific user among the certificates is acquired from a user device, performing (i) a process of instructing the user device to generate a public key and a private key of the specific user and transmit the public key to the authentication-supporting server, (ii) a process of storing the specific certificate including the public key such that the specific certificate corresponds to the personal information, and (iii) a process of determining whether one of current anchoring conditions for registering a specific transaction in the blockchain network is satisfied, wherein the current anchoring conditions include one of a condition that a predetermined number of the certificates, including the specific certificate, are stored after a previous anchoring condition is satisfied and a condition that a predetermined time is lapsed, after the previous anchoring condition is satisfied; (b) if said one of the current anchoring conditions is satisfied, performing a process of generating a specific root hash value by applying a Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates stored after the previous anchoring condition is satisfied; and. (c) performing (i) one of (i-1) a process of storing the specific transaction including the specific root hash value in a distributed database on the blockchain network, and (i-2) a process of instructing at least one of blockchain nodes in the blockchain network to store the specific transaction in the distributed database, and (ii) a process of acquiring a specific transaction ID representing a location of the specific transaction on the distributed database, and an authentication-supporting server using the same.

BACKGROUND OF THE INVENTION

In general, a certificate is electronic information issued by a certificate authority (CA) for the purpose of confirming an identity of a user, and preventing transaction denials or forgery and falsification of a document upon the use of services in the various industrial, fields, representing a kind of certificate of seal impression for a digital transaction. Such a certificate contains a version, a serial number, an effective period, an issuing institution of the certificate, information on verification of an electronic signature of a user, a name of the user, information on identification confirmation, an electronic signing method, etc.

The certificate is used (refer to Cited Patent Literature 1) in a public key infrastructure (PKI) as a standard security method.

The PKI is a set of roles, policies, and procedures needed to create, manage, distribute, use, store, and revoke certificates and manage public key encryption.

However, in the PKI, the private key used, for decryption is generated and provided by the CA who is just a third party, not the user, therefore it is open to hacking, and as the user's private key exists in the form of a file at a storing location standardized by a soft token-based storing method, it is easy to copy and collect automatically the private key file and this has a risk of financial damages and user information theft caused by a leaked private key. Therefore, the CA who provides the generated private key to the user must have a certificate issuing system with a strong security to minimize hacking attempts, which requires operation and maintenance and thus causes a high cost of the issuance.

In addition, the certificate can be used only when ActiveX controls are installed in advance, for the purpose of additional security for the user authentication process through a web browser. However, to install, the ActiveX controls on a personal computer (PC), a security level of the PC must be lowered for the ActiveX controls to access resources including files, registry, etc. Due to the lowered security level of the user's PC caused by the Active X controls, the PC becomes vulnerable to the dangerous environment such as hacking.

Each of the problems associated with the certificate is resolved by the certificate issuance system based on the blockchain (refer to Cited Patent Literature 2), and a method using the same, and by the certificate authenticating system based on the blockchain and a method using the same, from the applicant.

The conventional certificate issuance system based on the blockchain and the method using the same, and the conventional certificate authentication system based on the blockchain and the method using the same disclose a method for directly generating a public hey and a private key for the certificate within a user device operated by a user, the user device generating the public and private keys while the network is disconnected, preventing possible leakage of the keys by storing and managing the private key encrypted together with a photo image and a password selected by the user, where the public key, which requires constant maintenance, is stored and managed in the blockchain of the digital wallet in the blockchain server by using a distributed database based on a peer-to-peer network (P2P), not a server managed by the CA, thus, an additional cost is minimized which is required for maintenance of the certificate issuance system with the strong security against hacking, and performing authentication even without the ActiveX controls.

Despite these advantages, a conventional certificate issuance system and method based on blockchain, and a conventional certificate authentication system and method based, on the blockchain require an initial cost of issuance for storing and managing of the public key for the certificate need for the authentication of the certificate.

The initial cost is about 0.0001 bitcoin, and as of July 2015, 0.0001 bitcoin amounts to about mere 4 cents, however, this cost is charged every time the certificate based on the blockchain is issued, thus this becomes a problem as the cost of the issuance increases in proportion to the increase of the

Additionally, the conventional certificate issuance system and method and the conventional certificate authentication system and method register, store, and manage the public key in more than 0.1 million blockchain nodes to prevent forgery of the public key.

That is, the broadcast of the transaction information including the public key is defined by a protocol, and if the transaction information including the public key occurs, one node, i.e., a blockchain node, broadcasts initial transaction information including the public key to eight designated nodes, then each of the eight designated nodes chat received the information broadcasts again to another eight designated nodes in a pyramidic fashion, and the broadcast is completed when the information is transmitted to all of the blockchain nodes which have the digital wallets containing the blockchain required for bitcoin payment.

Due to these reasons, the conventional certificate issuance system and method and the conventional certificate authentication system and method have a risk of network overload caused by traffic of transaction information including the public keys when requests for registering the public keys rush in, and exposure of the public keys because the transaction information including the public keys stored in the blockchain nodes is open to public.

PRIOR ART Cited Patent Literature

Cited Patent Literature 1: Korean Patent Publication No. 10-0411448 registered on Dec. 3, 2003

Cited Patent Literature 2: Korean Patent Laid-Open Publication No. 10-1661930 filed on Aug. 3, 2015

SUMMARY OF THE INVENTION

It is an object of the present disclosure to solve all the aforementioned problems.

It is another object of the present disclosure to provide a certificate issuance system based on a blockchain network and a certificate issuance method based on the blockchain network using the same by eliminating a constructing cost, a cost to construct a system for issuing a certificate linked with top-grade security system to block hacking as much as possible, due to the fact that a public key for the certificate, which requires maintenance, is saved and managed on a blockchain network through a peer-to-peer (P2P) network based distributed database instead, of being saved and managed, on a certificate authority (CA) operating server, eliminating system-related costs such as operating and maintaining cost of the constructed system for issuing the certificate based on the blockchain network, and greatly reducing an issuing cost when issuing the certificate.

It is still another object of the present disclosure to provide the certificate issuance system based on the blockchain network and the certificate issuance method based on the blockchain network using the same by grouping users' public keys for the certificate as many as the predetermined number, compressing the grouped public keys, and registering transaction information that includes the grouped public keys list in order to minimise the network traffics, to thereby also minimize the network overload while registering the transaction information in the blockchain network in the process of issuing the certificate.

It is still yet another object of the present disclosure to provide the certificate issuance system based on the blockchain network and the certificate issuance method based on the blockchain network using the same capable of performing an authentication process, when issuing the certificate, of the certificate without registering the users' public keys in the blockchain network, and monitoring forgery and falsification of authentication related, information that includes the public key of the user.

In accordance with one aspect of the present disclosure, there is provided, a method for issuing one or more certificates based on a blockchain network, including steps of: (a) an authentication-supporting server, if personal information on a specific user for issuing a specific certificate of the specific user among the certificates is acquired from a user device, performing (i) a process of instructing the user device to generate a public key and a private key of the specific user and transmit the public key to the authentication supporting server, (ii) a process of storing the specific certificate including the public key such that the specific certificate corresponds to the personal information, and (iii) a process of determining whether one of current anchoring conditions for registering a specific transaction in the blockchain network is satisfied, wherein the current anchoring conditions include one of a condition that a predetermined number of the certificates, including the specific certificate, are stored after a previous anchoring condition is satisfied and a condition that a predetermined time is lapsed after the previous anchoring condition is satisfied; (b) the authentication-supporting server, if said one of the current anchoring conditions is satisfied, performing a process of generating a specific root hash value by applying a Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates stored after the previous anchoring condition is satisfied; and (c) the authentication-supporting server performing (i) one of (i-1) a process of storing the specific transaction including the specific root hash value in a distributed database on the blockchain network, and (i-2) a process of Instructing at least one of blockchain nodes in the blockchain network to store the specific transaction in the distributed database, and (ii) a process of acquiring a specific transaction ID representing a location of the specific transaction on the distributed database.

As one example, the method further comprises a step of: (d) the authentication-supporting server, if a request for verification of the specific certificate including identification information on the specific user is acquired, performing (i) a process of generating a specific root hash value for comparison by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values for comparison of each of the certificates corresponding to specific root hash identification information, by referring to the specific root hash identification information corresponding to the specific identification information on the specific user, wherein the specific root hash identification information includes information for identifying a specific root hash value for reference which is the specific root hash value generated at the step of (b); (ii) one of (ii-1) a process of retrieving from the distributed database the specific root hash value, as a specific root hash value for reference, included in the specific transaction corresponding to the specific transaction ID, and (ii-2) a process of instructing at least one of the blockchain nodes to retrieve from the distributed database the specific root hash value for reference included in the specific transaction corresponding to the specific transaction ID; and (iii) a process of confirming a validity of the specific certificate by referring to the specific root hash value for comparison and the specific root hash value for reference.

As one example, at the step of (d), the authentication-supporting server, if the specific root hash value for reference is determined as different from the specific roof hash value for comparison, compares (i) a specific hash value for reference included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for reference and (ii) a specific hash value for comparison included, in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for comparison, to thereby confirm the validity of the specific certificate.

As one example, at the step of (d), the authentication-supporting server, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) each of hash values for reference included in each of the leaf nodes corresponding to the specific root hash value for reference, and (ii) each of hash values for comparison included in each of the leaf nodes corresponding to the specific root hash value for comparison, to thereby determine at least one forged certificate, among the certificates, corresponding to the specific root hash identification information.

As one example, before the step of (b), the authentication-supporting server, if said one of the current anchoring conditions is satisfied, performs (i) one of (i-1)6 a process of retrieving from the distributed database each of previous root hash values for reference included in each of previous transactions corresponding to each of previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, and (i-2) a process of instructing the at least one of the blockchain nodes on the blockchain network to retrieve from the distributed database each of the previous root hash values for reference included in each of the previous transactions corresponding to each of the previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, (ii) a process of acquiring each of previous certificates corresponding to each of the previous root, hash values for reference, and a process of generating each of previous root hash values for comparison by applying the Merkle tree operation to each of leaf nodes including each, of previous hash values for comparison of said each of the previous certificates, and (iii) a process of comparing said each of the previous root hash values for comparison and said each of the previous root hash, values for reference, to thereby confirm a validity of the previous certificates.

As one example, at the step of (b), one of the leaf nodes includes a certain previous root hash value created right before said one of the current anchoring conditions is satisfied.

As one example, at the step of (b), the authentication-supporting server manages (i) specific root hash identification information which is information used for identifying the specific root hash value, and (ii) specific node index information which is information on (ii-1) each of locations of each of the leaf nodes including each of the hash values of each of the certificates and (ii-2) each of the hash values of each of the certificates.

In accordance with another aspect of the present disclosure, there is provided a method for issuing one or more certificates based on a blockchain network, including steps of: (a) a certificate-managing server, if a registration request including identification information on a specific user and a public key of the specific user is acquired, wherein an issuance-requesting server transmits to a user device a key-generating signal instructing creation of the public key and a private key of the specific user in response to personal information on the specific user transmitted, from the user device and wherein the issuance-requesting server generates the registration request by referring to the specific identification information on the specific user corresponding to the personal information and the public key sent from the user device, performing (i) a process of storing a specific certificate including the public key such that the specific certificate corresponds to the specific identification information on the specific user, and (ii) a process of determining whether at least one of current anchoring conditions for registering a specific transaction in the blockchain network is satisfied, wherein the current anchoring conditions include one of a condition that a predetermined number of the certificates, including the specific certificate, are stored after a previous anchoring condition is satisfied and a condition that a predetermined time is lapsed after the previous anchoring condition is satisfied; (b) the certificate-managing server, if said one of the current anchoring conditions is satisfied, performing a process of generating a specific root hash value by applying a Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates stored after the previous anchoring condition is satisfied; and (c) the certificate-managing server performing (i) one of (i-1) a process of storing the specific transaction including the specific root hash value in a distributed database on the blockchain network, and (i-2) a process of instructing at least one of blockchain nodes in the blockchain network to store the specific transaction in the distributed database, and. (ii) a process of acquiring a specific transaction ID representing a location of the specific transaction on the distributed database.

As one example, the method further comprises a step of: (d) the certificate-managing server, if a request for verification of the specific certificate including identification information on the specific user is acquired, performing (i) a process of generating a specific root hash value for comparison by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values for comparison of each of the certificates corresponding to specific root hash identification information, by referring to the specific root hash identification information corresponding to the specific identification information on the specific user, wherein the specific root hash identification information includes information for identifying a specific root hash value for reference which is the specific root hash value generated at the step of (b), (ii) one of (ii-1) a process of retrieving from the distributed database the specific root hash value, as a specific root hash value for reference, included in the specific, transaction corresponding to the specific: transaction ID, and (ii-2) a process of instructing at least one of the blockchain nodes to retrieve from the distributed database the specific root hash, value for reference included in the specific transaction, corresponding to the specific transaction ID; and (iii) a process of confirming a validity of the specific certificate by referring to the specific root hash value for comparison and the specific root hash value for reference.

As one example, at the step of (d), the certificate-managing server, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) a specific hash value for reference included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for reference and (ii) a specific bash value for comparison included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for comparison, to thereby confirm the validity of the specific certificate.

As one example, at the step of (d), the certificate-managing server, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) each of hash values for reference included in each of the leaf nodes corresponding to the specific root hash value for reference, and (ii) each of hash values for comparison included in each of the leaf nodes corresponding to the specific root hash value for comparison, to thereby determine at least one forged certificate, among the certificates, corresponding to the specific root hash identification information.

As one example, before the step of (b), the certificate-managing server, if said one of the current anchoring conditions is satisfied, performs (i) one of (i-i) a process of retrieving from the distributed database each of previous root hash values for reference included in each of previous transactions corresponding to each of previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, and (i-2) a process of instructing the at least one of the blockchain nodes on the blockchain network to retrieve from the distributed database each of the previous root hash values for reference included in each of the previous transactions corresponding to each of the previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, (ii) a process of acquiring each of previous certificates corresponding to each of the previous root hash values for reference, and a process of generating each of previous root hash values for comparison by applying the Merkle tree operation to each of leaf nodes including each of previous hash values for comparison of said each of the previous certificates, and (iii) a process of comparing said each of the previous root hash values for comparison and said each of the previous root hash values for reference, to thereby confirm a validity of the previous certificates.

As one example, at the step of (b), one of the leaf nodes includes a certain previous root hash value created, right before said one of the current anchoring conditions is satisfied.

As one example, at the step of (b), the certificate-managing server manages (i) specific root hash identification information which is information used for identifying the specific root hash value, and (ii) specific node index information which is information on (ii-1) each of locations of each of the leaf nodes including each of the hash values of each of the certificates and (ii-2) each of the hash values of each of the certificates.

In accordance with still another aspect of the present disclosure, there is provided an authentication-supporting server for issuing one or more certificates based on a blockchain network, including: a communication part for acquiring personal information on a specific user for issuing a specific certificate of the specific user among the certificates from a user device; and a processor for performing (I) a process of instructing the user device to generate a public key and a private key of the specific user and transmit the public key to the authentication-supporting server, (II) a process of storing the specific certificate including the public key such that the specific certificate corresponds to the personal information, and (III) a process of determining whether one of current anchoring conditions for registering a specific transaction in the blockchain network is satisfied, wherein the current anchoring conditions include one of a condition that a predetermined number of the certificates, including the specific certificate, are stored after a previous anchoring condition is satisfied and a condition that a predetermined time is lapsed after the previous anchoring condition is satisfied, (IV) if said one of the current anchoring conditions is satisfied, a process of generating a specific root hash value by applying a Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates stored, after the previous anchoring condition is satisfied, (V) one of (V-I) a process of storing the specific transaction including the specific root hash value in a distributed database on the blockchain network, and (V-2) a process of instructing at least one of blockchain nodes in the blockchain network to store the specific transaction in the distributed database, and (VI) a process of acquiring a specific transaction ID representing a location of the specific transaction on the distributed database.

As one example, the authentication-supporting server further comprises processes of: (VII) if a request for verification of the specific certificate including identification information on the specific user is acquired, generating a specific root hash value for comparison by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values for comparison of each of the certificates corresponding to specific root hash identification information, by referring to the specific root hash identification information corresponding to the specific identification information on the specific user, wherein the specific root hash identification information includes information for identifying a specific root hash value for reference which is the specific root hash value generated at the process of (IV), (VIII) one of (VIII-1) retrieving from the distributed database the specific root hash value, as a specific root hash value for reference, included in the specific transaction corresponding to the specific transaction ID, and (VIII-2) instructing at least one of the blockchain nodes to retrieve from the distributed database the specific root hash value for reference included in the specific transaction corresponding to the specific transaction ID, and (IX) confirming a validity of the specific certificate by referring to the specific root hash value for comparison and the specific root hash value for reference.

As one example, at the process of (IX), the processor, if the specific roof hash value for reference is determined as different from the specific root hash value for comparison, compares (i) a specific hash value for reference included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for reference and (ii) a specific hash value for comparison included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for comparison, to thereby confirm the validity of the specific certificate.

As one example, at the process of (IX), the processor, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) each of hash values for reference included in each of the leaf nodes corresponding to the specific root hash value for reference, and (ii) each of hash values for comparison included in each of the leaf nodes corresponding to the specific root hash value for comparison, to thereby determine at least one forged certificate, among the certificates, corresponding to the specific root hash identification information.

As one example, before the process of (IV), the processor, if said one of the current anchoring conditions is satisfied, performs (i) one of (i-1) a process of retrieving from the distributed database each of previous root hash values for reference included in each of previous transactions corresponding to each of previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, and (i-2) a process of instructing the at least one of the blockchain nodes on the blockchain network to retrieve from the distributed database each of the previous root hash values for reference included in each of the previous transactions corresponding to each of the previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, (ii) a process of acquiring each of previous certificates corresponding to each of the previous root hash values for reference, and a process of generating each of previous root hash values for comparison by applying the Merkle tree operation to each of leaf nodes including each of previous hash values for comparison of said each of the previous certificates, and (iii) a process of comparing said each of the previous root hash values for comparison and said each of the previous roof hash values for reference, to thereby confirm a validity of the previous certificates.

As one example, at the process of (IV), one of the leaf nodes includes a certain previous root hash value created right before said one of the current anchoring conditions is satisfied.

As one example, at the process of (IV), the processor manages (i) specific root hash identification information which is information used for identifying the specific root hash value, and (ii) specific node index information which is information on (ii-1) each of locations of each of the leaf nodes including each of the hash values of each of the certificates and (ii-2) each of the hash values of each of the certificates.

In accordance with still yet another aspect of the present disclosure, there is provided, a certificate-managing server for issuing one or more certificates based on a blockchain network, including: a communication part for acquiring a registration request including identification information on a specific user and a public key of the specific user, wherein an issuance-requesting server transmits to a user device a key-generating signal instructing creation of the public key and a private key of the specific user in response to personal information on the specific user transmitted from the user device and wherein the issuance-requesting server generates the registration request by referring to the specific identification information on the specific user corresponding to the personal information and the public key sent from the user device; and a processor for performing (I) a process of storing a specific certificate corresponds to the specific identification information on the specific user, and (II) a process of determining whether at least one of current anchoring conditions for registering a specific transaction in the blockchain network is satisfied, wherein the current anchoring conditions include one of a condition that a predetermined number of the certificates, including the specific certificate, are stored after a previous anchoring condition is satisfied and a condition that a predetermined time is lapsed after the previous anchoring condition is satisfied, (III) if said one of the current anchoring conditions is satisfied, a process of generating a specific root hash value by applying a Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates stored after the previous anchoring condition is satisfied, (IV) one of (XV-1) a process of storing the specific transaction including the specific root hash value in a distributed database on the blockchain network, and (IV-2) a process of instructing at least one of blockchain nodes in the blockchain network to store the specific transaction in the distributed database, and (V) a process of acquiring a specific transaction ID representing a location of the specific transaction on the distributed database.

As one example, the certificate-managing server further comprises processes of: (VI) if a request for verification of the specific certificate including identification in formation on the specific user is acquired., generating a specific root hash, value for comparison by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values for comparison of each of the certificates corresponding to specific root hash identification information, by referring to the specific root hash identification information corresponding to the specific identification information on the specific user, wherein the specific root hash identification information includes information for identifying a specific root hash value for reference which is the specific root hash value generated at the process of (III), (VII) one of (VII-1) retrieving from the distributed database the specific root hash value, as a specific root hash value for reference, included in the specific transaction corresponding to the specific transaction ID, and (VII-2) instructing at least one of the blockchain nodes to retrieve from the distributed database the specific root hash value for reference included in the specific transaction corresponding to the specific transaction ID, and (VIII) confirming a validity of the specific certificate by referring to the specific root hash value for comparison, and the specific root hash value for reference.

As one example, at the process of (VIII), the processor, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) a specific hash value for reference included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for reference and (ii) a specific hash value for comparison included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for comparison, to thereby confirm the validity of the specific certificate.

As one example, at the process of (VIII), the processor, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) each of hash values for reference included in each of the leaf nodes corresponding to the specific root hash value for reference, and (ii) each of hash values for comparison included in each of the leaf nodes corresponding to the specific root hash value for comparison, to thereby determine at least one forged certificate, among the certificates, corresponding to the specific root hash identification information.

As one example, before the process of (III), the processor, if said one of the current anchoring conditions is satisfied, performs (1) one of (i-1) a process of retrieving from the distributed database each of previous root hash values for reference included in each of previous transactions corresponding to each of previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, and (i-2) a process of instructing the at least one of the blockchain nodes on the blockchain network to retrieve from the distributed, database each of the previous root hash values for reference included in each of the previous transactions corresponding to each of the previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, (ii) a process of acquiring each of previous certificates corresponding to each of the previous root hash values for reference, and a process of generating each of previous root hash values for comparison by applying the Merkle tree operation to each of leaf nodes including each of previous hash values for comparison of said each of the previous certificates, and (iii) a process of comparing said each of the previous root hash values for comparison and said, each of the previous root hash values for reference, to thereby confirm a validity of the previous certificates.

As one example, at the process of (III), one of the leaf nodes includes a certain previous root hash value created right before said one of the current anchoring conditions is

As one example, at the process of (III), the processor manages (i) specific root hash identification information which is information used for identifying the specific root hash value, and (ii) specific node index information which is information on. (ii-1) each of locations of each of the leaf nodes including each of the hash values of each of the certificates and. (ii-2) each of the hash values of each of the certificates.

BRIEF DESCRIPTION OP THE DRAWINGS

The above and other objects and features of the present, disclosure will become apparent from the following description of preferred embodiments given in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram schematically illustrating a system for issuing a specific certificate based, on a blockchain network in accordance with one example embodiment of the present disclosure.

FIG. 2 is a block diagram schematically illustrating a detailed configuration of a specific user device of the system for issuing the specific certificate based on the blockchain network in accordance with one example embodiment of the present disclosure.

FIG. 3 is a block diagram schematically illustrating a detailed configuration of an issuance-requesting server of the system for issuing the specific certificate based on the blockchain network in accordance with one example embodiment of the present disclosure.

FIG. 4 is a block diagram schematically illustrating a detailed configuration of a certificate-managing server of the system, for issuing the specific certificate based on the blockchain network in accordance with one example embodiment of the present disclosure.

FIGS. 5 to 8 are flow charts schematically illustrating a process of issuing the specific certificate by using the system for issuing the specific certificate based on the blockchain network in accordance with one example embodiment of the present disclosure.

FIG. 9 is a block diagram schematically illustrating a system, for authenticating the specific certificate based on the blockchain network in accordance with one example embodiment of the present disclosure.

FIG. 10 is a block diagram schematically illustrating a detailed configuration of an authentication-requesting server of the system for authenticating the specific certificate based on the blockchain network in accordance with one example embodiment of the present disclosure.

FIGS. 11 to 16 are flow charts schematically illustrating a process of authenticating the specific certificate by using the system for authenticating the specific certificate based on the blockchain network in accordance with one example embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Detailed explanation on the present disclosure to foe made below refer to attached drawings and diagrams illustrated as specific embodiment: examples under which the present disclosure may be implemented to make clear of purposes, technical solutions, and advantages of the present disclosure. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention.

Besides, in the detailed description and claims of the present disclosure, a term “include” and its variations are components or steps. Other objects, benefits and features of the present disclosure will be revealed to one skilled in the art, partially from the specification and partially from the implementation of the present disclosure. The following examples and drawings will be provided as examples but they are not intended to limit the present disclosure.

Moreover, the present disclosure covers all possible combinations of example embodiments indicated in this specification. It is to foe understood that the various embodiments of the present disclosure, although different, are not necessarily mutually exclusive. For example, a particular feature, structure, or characteristic described herein in connection with one embodiment may be implemented within, other embodiments without departing from the spirit and scope of the present disclosure, in addition, it is to be understood that disclosed embodiment may be modified without departing from the spirit and scope of the present disclosure. The following detailed, description is, therefore, not to be taken in a limiting sense, and the scope of the present disclosure is defined only by the appended claims, appropriately interpreted, along with the full range of equivalents to which the claims are entitled. In the drawings, like numerals refer to the same or similar functionality throughout the several views.

To allow those skilled in the art to the present disclosure to be carried out easily, the example embodiments of the present disclosure by referring to attached diagrams will be explained in detail as shown below.

Throughout the present disclosure, every processor, every memory, every storage, or any other computing components are described as separate components, however, said every processor, said every memory, said every storage, or said any other computing components may be configured as a single device or any other combinations thereof.

Also, throughout the present disclosure, a temporal order of acquiring, comparing, determining, extracting, generating, hashing, processing, retrieving, storing, or transmitting ‘something for reference’ and ‘something for comparison’ is not limited.

The present disclosure includes part for issuance and part for authentication of a specific certificate based on a blockchain network.

Herein, FIGS. 1 to 3 may illustrate a system and a method for issuing the specific certificate based on the blockchain network.

As illustrated, the system for issuing the specific certificate based on the blockchain network in accordance with the present disclosure may include a specific user device 100, an issuance-requesting server 200, a certificate-managing server 300, and the blockchain network 400.

First, the specific user device 100 may generate a public key and a private key of a specific user corresponding to a public key for the specific certificate and a private key for the specific certificate, and may transmit the generated public key and personal information on the specific user required for issuing the specific certificate based on the blockchain network. Herein, the personal information may include at least one of a name of the specific user, a birth date of the specific user, a phone number of the specific user, and an e-mail address of the specific user.

The specific user device 100 performing such functions may be comprised of a key-generating engine 110 to generate the public key and the private key of the specific user, a memory 120 where the generated private key is stored, a first encrypting engine 130, a first hashing engine 140, a first decrypting engine 160, and a controlling part 150 which manages the key-generating engine 110, the first encrypting engine 130, the first hashing engine 140, and the first decrypting engine 160. In addition, the specific user device 100 may include a communication part (not illustrated) and a processor including the controlling part 150.

If the specific user device 100 is in a form of desktop computer, such as a PC, then the key-generating engine 110, the first encrypting engine 130, the first hashing engine 140, and the first decrypting engine 160 may be loaded in a form of application, and if the specific user device 100 is a mobile device such as a smart phone that is able to access the Internet, these engines may be loaded in a form of application exclusively used for mobile devices.

Before generating the public key and the private key of the specific user, the specific user device 100 may confirm whether the specific user operating the specific user device 100 has registered specific identification information on the specific user in the issuance-requesting server 200.

In order to do so, a first DB part 210 may be deployed on the issuance-requesting server 200, and the specific identification information on the specific user who is operating the specific user device 100 is stored in the first DB part 210 which may also include a DB 211 for user identification which contains the personal information on the specific user that has been matched with the specific identification information on the specific user.

Then, the specific user device 100 may transmit the personal information to the issuance-requesting server 200 to request the issuance of the specific certificate based on the blockchain network. The issuance-requesting server 200, then, may compare the received, personal information with information stored in the DB 211 for user identification, and if identical information is determined, as stored, may generate and transmit a key-generating signal that instructs creation of the public key and the private key of the specific user to the specific user device 100.

If the key-generating signal is acquired from the issuance-requesting server 200, the specific user device 100 may instruct the key-generating engine 110 to generate the public key and the private key of the specific user, where the specific user device 100 may allow the public key and the private key to be generated while a network is being disconnected, to prevent possible leakage of the keys.

The issuance-requesting server 200 may acquire the personal information and the public key of the specific user from the specific user device 100, and may transmit a registration-requesting signal including the acquired public key and identification information corresponding to the acquired personal information to the certificate-managing server 300 for managing the specific certificate described later. In addition, the issuance-requesting server 200 may include a communication part (not illustrated) and a processor (not illustrated). The issuance-requesting server 200 typically achieves desired system performance by using combinations of at least one computing device and at least one computer software, e.g., a computer processor, a memory, a storage, an input device, an output device, or any other conventional, computing components, an electronic communication device such as a router or a switch, an electronic information storage system such as a network-attached storage (NAS) device and a storage area network (SAN) as the computing device and any instructions that allow the computing device to function in a specific way as the computer software.

Herein, the issuance-requesting server 200 may include a second, hashing engine 220 which may hash the personal information, to thereby generate and transmit the specific identification information on the specific user to the certificate-managing server 300.

The issuance-requesting server 200 with such functions may be a server of a company whose service requires the specific certificate, like a server of a bank or a securities firm, a server of a government institution, or a server of an on-line Internet shopping mall.

The certificate-managing server 300 may store sequentially and cumulatively in the DB 311 for registration information the specific identification information on the specific user and the specific certificate of the specific electronic information storage system such as a networks user including the public key of the specific user contained in the registration-requesting signal from the issuance-requesting server 200 such that the specific certificate corresponds to the specific identification information, on the specific user, and if one of current anchoring conditions for registering a specific transaction in the blockchain network 400 is satisfied, may instruct a third, hashing engine 320 to hash previous certificates stored through previous transactions before the specific transaction, for example, hash the previous certificates in the order of their storing, may apply a Merkle tree operation to each of leaf nodes including each of hash values of the certificates to thereby generate a specific root hash value for reference, may instruct a transaction-processing engine 330 to generate the specific transaction including the specific root hash value for reference and generate a specific transaction ID used as a key value to search for the specific transaction, and transmit the specific transaction. In addition, the certificate-managing server 300 may include a communication part (not illustrated) and a processor (not illustrated). The certificate-managing server 300 typically achieves desired system performance by using combinations of at least one computing device and at least one computer software, e.g., a computer processor, a memory, a storage, an input device, an output, device, or any other conventional computing components, an electronic communication device such as a router or a switch, an electronic information storage system such as a network-attached storage (HAS) device and a storage area network (SAN) as the computing device and any instructions that allow the computing device to function in a specific way as the computer software.

Herein, the DE 311 for registration information may be managed by a second DB part 310.

Also, the DB 311 for registration information may store all of the certificates, all pieces of root hash identification information used for identifying ail of the root hash values for reference, and all pieces of node index information, as corresponding to ail pieces of the identification information, including (i) each of all of the hash values corresponding to each of all of the leaf nodes used, for the Merkle tree operation of all of the root hash values for reference, and (ii) all pieces of the identification information on each of all of the users corresponding to each of all of the leaf nodes.

Also, the second DB part 310 may include a DB 312 for monitoring forgery where all of transaction IDs generated every time the transaction is created at the transaction-processing engine 330, and their corresponding root hash identification information, are stored cumulatively.

Also, if one of the current anchoring conditions is satisfied, the certificate-managing server 300 may monitor whether one of next anchoring conditions is satisfied for each of subsequent certificates corresponding to the identification information stored in the DB 311 for registration information, after said one of the current anchoring conditions is satisfied, to thereby allow the subsequent certificates based on the blockchain network to be issued to new users.

Herein, the current anchoring conditions include one of a condition that a predetermined number of the certificates are stored after a previous anchoring condition is satisfied and a condition that a predetermined time is lapsed after the previous anchoring condition is satisfied. By processing the transactions of the certificates of the users stored between a previous and a current anchoring conditions, the network traffic may be minimized and the network overload may be reduced.

Meanwhile, the certificate-managing server 300 may monitor the certificates stored, in the DB 311 for registration information to detect forgery during the process of the issuance of the certificates based on the blockchain network, to thereby react by detecting forgery of any certificates due to illegal activities like hacking.

For this purpose, if one of the current anchoring conditions is satisfied, the certificate-managing server 300 may extract all of previous transaction IDs stored in the DB 312 for monitoring forgery, and may transmit all of the previous transaction IDs to the blockchain network 400 comprised of blockchain nodes 410.

At least one of the blockchain nodes 410 in the blockchain nodes 400 may retrieve the previous transactions corresponding to the previous transaction IDs from the distributed database stored in the blockchain network 400, i.e., the blockchain nodes 410, by referring to the transmitted previous transaction IDs, may extract each of previous root hash values for reference included in each of the previous transactions, and may transmit each of the previous root hash values for reference to the certificate-managing server 300.

Thereafter, the certificate-managing server 300 may acquire each of the previous root hash values for reference, and may identify each of the previous certificates, corresponding to previous identification information, stored in the DB 311 for registration information as corresponding to each of the previous root hash values for reference. That is, the certificate-managing server 300 may acquire each of previous root hash identification information for reference corresponding to each of the previous root hash values for reference, and may organize previous certificates to be corresponding to leaf nodes of the previous node index information, by referring to the previous identification information corresponding to each of the previous root hash identification information for reference.

Then, the certificate-managing server 300 may instruct the third hashing engine 320 to apply the Merkle tree operation to leaf nodes including previous hash values for comparison of each of the previous certificates, to thereby generate each of previous root hash values for comparison.

Thereafter, the certificate-managing server 300 may pair the transmitted previous root hash values for reference with the generated previous root hash values for comparison corresponding thereto.

Thereafter, the certificate-managing server 300 may compare the previous root hash values for reference with the previous root hash values for comparison, to thereby determine whether the two hash values are the same.

If every previous root hash value is determined a s identical to each other within each pair of the two previous root hash values, the certificate-managing server 300 may determine that there is no forgery of information related to the previous certificates, and may allow the specific transaction to be generated.

However, if there is a pair whose previous root hash values are different, the certificate-managing server 300 may determine that forgery of the information related to the previous certificates occurred, and may prevent the specific transaction from being generated, and may perform processes of handling the forgery.

In addition, the certificate-managing server 300 may instruct the third hashing engine 320 to generate root hash identification information used for identifying the previous root hash values, and Merkle tree information, on the previous roof hash values, i.e., previous node index information.

Also, the certificate-managing server 30 0 may store the specific root hash identification information in the DB 311 identification information on the specific user, and may further store the specific root hash identification information in the DB 312 for monitoring forgery.

Then, the issuance-requesting server 200 may store the previous transaction IDs generated at the transaction-processing engine 320 in the DB 312 for monitoring forgery, to thereby allow the previous transaction IDs and their corresponding previous root hash identification information to be stored and managed in the DB 312 for monitoring forgery.

Meanwhile, the more the root hash values in the blockchain network 400 comprised of the blockchain nodes 410 are connected to each other, the more difficult the forgery

Herein, on condition that a certain previous root hash value for reference, created right before said one of the current anchoring conditions is satisfied, has been stored in a predetermined leaf node among leaf nodes corresponding to the specific root hash value for reference to be generated, the certificate-managing server 300 may instruct the third hashing engine 320 to apply the Merkle tree operation to each of the leaf nodes, one of which includes the certain previous roof hash value for reference, to thereby generate the specific root hash value for reference.

In case all of the root hash values for reference included in all of the transactions stored in the blockchain network 400 of the blockchain nodes 410, their structures show a connected chain of all of the root hash values from the firstly-registered to the lastly-registered, thus, as the number of ail of the transactions stored in the blockchain network 400 of the blockchain nodes 410 increases, the certificate-managing server 300 may make it difficult to forge the certificates caused by the illegal activities.

Also, auditors of the certificates who are related to the government institutions may request an audit via a verification-requesting device 500 to confirm, whether the information related to the certificates, issued, in accordance with, the present disclosure, is forged.

For this purpose, the auditors may instruct the verification-requesting device 500 to transmit a request for monitoring the specific certificate of the specific user to the issuance-requesting server 200.

Hereafter, the issuance-requesting server 200 may extract the specific identification information on the specific user who requested the monitoring of the specific certificate from the DE 211 for user identification, and transmit the specific identification information to the certificate-managing server 300.

The certificate-managing server 300 may confirm a presence of the specific node index information on the specific user in the DB 311 for registration information by referring to the specific identification information on the specific user who requested the monitoring.

Thereafter, if the specific node index information on the specific user does not exist, the certificate-managing server 300 may instruct the third hashing engine 320 to hash, for example, sequentially hash in the order of storing, the certificates stored sequentially in the DB 311 for registration information that do not correspond to any node index information, to thereby generate each of hash values of each of the certificates.

Thereafter, the certificate-managing server 300 may apply the Merkle tree operation to each of leaf nodes including each of the hash values of each of the certificates created by the third hashing engine 320, to thereby generate the specific root hash value for reference and may generate (i) the specific root hash identification information used for identifying the specific root hash value for reference, and (ii) specific node index information on (ii-1) each of locations of each of the leaf nodes including each of the hash values of each of the certificates and (ii-2) each of the hash values of each of the certificates.

Thereafter, the certificate-managing server 300 may instruct the transaction-processing engine 320 to generate (i) the specific transaction including the specific root hash value for reference and (ii) the specific transaction ID used as a key value to search for the specific transaction, and transmit the specific transaction to the blockchain network 400 comprised of the blockchain nodes 410.

The blockchain network 400 comprised of the blockchain nodes 410 may store the transmitted specific transaction in the blockchain network 400, that is, the distributed database of each of the blockchain nodes 410.

And if the specific node index information on the specific user is determined as present, the certificate-managing server 300 may instruct the third hashing engine 320 to hash all of the certificates corresponding to the specific root hash identification information, to thereby generate each of the hash values for comparison by referring to the specific root hash identification information corresponding to the specific identification information on the specific user, and apply the Merkle tree operation to each of the leaf nodes, to thereby generate the specific root hash value for comparison by referring to the specific node index information including each of the hash values for comparison. That is, the certificate-managing server 300 may apply the Merkle tree operation to each of the leaf nodes including each of the hash values for comparison of each of the certificates corresponding to the specific root hash identification information, to thereby generate the specific root hash value for comparison, by referring to specific root hash identification information corresponding to the specific identification information on the specific user.

Thereafter, the certificate-managing server 300 may specific root hash identification information corresponding to the specific identification information on the specific user and may transmit the specific transaction ID to the blockchain network 400 comprised of the blockchain nodes 410. Herein, the specific transaction ID may be acquired by any one of the blockchain network 400 comprised of the blockchain nodes 410 distributed throughout the world, and may be acquired by a node pre-designated for efficiency.

Thereafter, at least one blockchain node among the blockchain nodes 410 may retrieve the specific transaction from the distributed database of the blockchain network 400 by referring to the specific transaction ID, may extract the specific root hash value for reference included in the retrieved specific transaction, and may transmit the specific root hash value for reference to the certificate-managing server 300.

Thereafter, the certificate-managing server 300 may acquire the specific root hash value for reference, and may compare the acquired specific root hash value for reference with the specific root hash value for comparison, to thereby determine whether the two hash values are identical to each other.

Then, if the specific root hash value for reference and the specific root hash value for comparison are identical with each other, the certificate-managing server 300 may compare (i) a specific hash value for reference included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for reference and (ii) a specific hash value for comparison included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for comparison, and if the specific hash value for reference and the specific hash value for comparison are identical, the certificate-managing server 300 may allow a message, representing the specific certificate of the specific user is authentic, to be transmitted to the verification-requesting device 500.

On the other hand, if the specific root hash value for reference and the specific root hash value for comparison are not identical to each other, then the certificate-managing server 300 may compare, for all the leaf nodes, (i) each of hash values of each of the certificates in each of the leaf nodes used to calculate the specific root hash value for reference corresponding to the specific hash value for reference, and (ii) its corresponding each of hash values of each of the certificates in each of the leaf nodes used to calculate the specific root hash value for comparison corresponding to the specific hash value for comparison, and identify one or more certain leaf nodes, which have different hash values with each other, among all the leaf nodes.

Thereafter, if one of the leaf nodes which includes a different hash value corresponds to the specific certificate of the specific user, the certificate-managing server 300 may allow a message, representing the specific certificate of the specific user is forged, to be transmitted to the verification-requesting device 500.

Also, if the leaf node including the different hash value of the specific certificate does not correspond to the specific certificate of the specific user, the certificate-managing server 300 may allow a message, representing the specific certificate of the specific user is not forged, to be transmitted to the verification-requesting device 500.

Although the issuance-requesting server 200 and the certificate-managing server 300 are described as separate devices in the above description, a single server, i.e., an authentication-supporting server 2000, may function as the issuance-requesting server 200 and the certificate-managing server 300.

That is, the authentication-supporting server 2000 may include a communication part (not illustrated) and a processor (not illustrated). Identical reference numerals are for convenience of explanation but not intended for representing sameness of separate devices. Further, in accordance with another example embodiment of the present disclosure, the method may be performed by the authentication-supporting server 2000 or another server of a different configuration. Further, the authentication-supporting server 2000 may be servers corresponding to each of nodes of the blockchain network 400, or may be a server managing each of the node of the blockchain network 400, or may be a transaction server.

Specifically, the authentication-supporting server 2000 typically achieves desired system performance by using combinations of at least one computing device and at least one computer software, e.g., a computer processor, a memory, a storage, an input device, an output device, or any other conventional computing components, an electronic communication device such as a router or a switch, an electronic information storage system such as a network-attached storage (NAS) device and a storage area network (SAN) as the computing device and any instructions that allow the computing device to function in a specific way as the computer software.

The communication part of such devices may transmit requests to and receive responses from other linked devices. As one example, such requests and responses may be carried out by the same TCP session, but the scope of the present disclosure is not limited thereto. For example, they could be transmitted and received as UDP datagrams.

Also, the processor of such devices may include hardware configuration of MPU (Micro Processing Unit) or CPU (Central Processing Unit), cache memory, data, bus, etc. Additionally, OS and software configuration of applications that achieve specific purposes may be further included.

A process of the issuance of the specific certificate based on the blockchain network by using the system for issuing the specific certificate based on the blockchain network in accordance with the present disclosure is described, as follows.

First, the specific user may access the issuance-requesting server 200 by way of the specific user device 100 and may transmit specific personal information for the issuance of the specific certificate based on the blockchain network, to thereby request the issuance, at a step of S100.

The issuance-requesting server 200 may confirm the acquired specific personal information, may create a key-generating signal for instructing a creation of a private key for the specific certificate and a public key for the specific certificate, and may transmit the key-generating signal to the specific user device 100 which requested, the issuance of the specific certificate based on the blockchain network, at a step of S110.

If the key-generating signal is received, the specific user device 100 may instruct a key-generating engine 110 to generate the public key and the private key of the specific user, may store the private key in the memory 120, and may transmit the public key to the issuance-requesting server 200, at a step of S120.

The issuance-requesting server 200 may acquire the public key of the specific user, may send a registration-requesting signal including the specific identification information on the specific user corresponding to the specific personal information on the specific user and the public key to the certificate-managing server 300, at a step of S130, and herein, the issuance-requesting server 200 may instruct the second hashing engine 220 to hash the specific personal information, to thereby generate the specific identification information on the specific user.

If the registration-requesting signal including the public key and the specific identification information on the specific user for the issuance are acquired, the certificate-managing server 300 may sequentially and cumulatively store the specific identification information on the specific user and the specific certificate including the public key of the specific user in the DB 311 for registration information such that the specific certificate corresponds to the specific identification information on the specific user, at a step of S140.

Thereafter, the certificate-managing server 300 may confirm whether one of the current anchoring conditions is met, at a step of S150. That is, the certificate-managing server 300 may monitor whether one of the current anchoring conditions is satisfied to register the specific transaction in the blockchain network 400 while storing the certificates. Herein, the current anchoring conditions include one of a condition that a predetermined number of the certificates are stored after a previous anchoring condition is satisfied and a condition that a predetermined, time is lapsed, after the previous anchoring condition is satisfied.

First, the certificate-managing server 300 may count the number of the certificates until the number reaches a predetermined number for calculation of the root hash values, or may store the certificates until one of the current anchoring conditions is satisfied.

Then, if one of the current anchoring conditions is satisfied, the certificate-managing server 300 may extract all of previous transaction IDs from the DB 312 for monitoring forgery, and may transmit all of the previous transaction IDs to the blockchain network 400 comprised of blockchain nodes 410, at a step of S160.

At least one of the blockchain nodes 410 in the blockchain nodes 400 may retrieve each of the previous transactions corresponding to the previous transaction IDs from the blockchain network 400, i.e., the distributed database, by referring to each of the transmitted previous transaction IDs, and may extract each of previous root hash values included in each of the previous transactions, at a step of S170.

Thereafter, the blockchain nodes 410 may transmit said each of the previous root hash values to the certificate-managing server 300, at a step of S180.

After acquiring each of the previous root hash values as the previous root hash values for reference, the certificate-managing server 300 may match each of the previous certificates, cumulatively stored in the DB 311 for registration, information with correspondence to the previous identification information, with each of the previous root hash values for reference, may instruct the third hashing engine 320 to hash each of the previous certificates, to thereby generate each of the previous hash values for comparison, and may apply the Merkle tree operation to each of the leaf nodes including each of the previous hash values for comparison, to thereby generate each of the previous root hash values for comparison, at a step of S190. That is, the certificate-managing server 300 may acquire each of the previous certificates corresponding to each of the previous root hash values for reference, and may apply the Merkle tree operation to each of the leaf nodes including each, of the previous hash values for comparison of each of the previous certificates, to thereby generate the previous root hash values for comparison.

Thereafter, the certificate-managing server 300 may compare said each of the previous root hash values for reference with said each of the previous root hash values for comparison sequentially, to thereby determine whether every each of compared pairs has identical previous root, hash values, at a step of S200. That is, the certificate-managing server 300 may determine whether each of the previous root hash values for reference retrieved from the blockchain network 400 is identical to each of its corresponding previous root hash values for comparison.

Meanwhile, if at least one part of each of the previous root hash values for reference retrieved from the blockchain network 400 is determined as not identical to each of its corresponding previous root hash values for comparison, then the certificate-managing server 300 may determine that said part of the previous certificates stored in the DB 311 for registration information is forged, at a step of S201, and may perform processes of handing the forgery.

Also, if each of the previous roof hash values for reference retrieved from the blockchain network 400 is determined as identical to each of its corresponding previous root hash values for comparison, then the certificate-managing server 300 may determine that the previous certificates are not forged, and may instruct the third hashing engine 320 to hash the certificates stored until one of the current anchoring conditions is satisfied, to thereby generate each of the hash

Then, the certificate-managing server 300 may instruct the third hashing engine 320 to apply the Merkle tree operation to each of the leaf nodes including each of the hash values for reference, to thereby generate the specific root hash value for reference, at a step of S210. Herein, the certificate-managing server 300 may generate the specific root hash identification information used for identifying the specific root hash value for reference, and the Merkle tree information on the specific root hash value for reference, i.e., the specific node index information which includes (i) each of the hash values corresponding to each of the leaf nodes used for the Merkle tree operation of the specific root hash value for reference, and (ii) the identification information on each of the users corresponding to each of the leaf nodes.

Thereafter, the certificate-managing server 300 may instruct the transaction-processing engine 320 to generate (i) the specific transaction including the specific root hash value for reference and (ii) the specific transaction ID used as a key value to search for the specific transaction, and transmit the specific transaction to the blockchain network 400 comprised of the blockchain nodes 410, at a step of S220.

Herein, on condition that the certain previous root hash value for reference, created right before said one of the current anchoring conditions is satisfied, has been stored in a predetermined leaf node among leaf nodes corresponding to the specific root hash value for reference to be generated, the certificate-managing server 300 may instruct the third hashing engine 320 to apply the Merkle tree operation to each of the leaf nodes, one of which includes the certain previous root hash value for reference, to thereby generate the specific root hash value for reference. That is, one of the leaf nodes may include the certain previous root hash value for reference created right before said one of the current anchoring conditions is satisfied.

At least one of the blockchain nodes 410 in the blockchain network 400 may store the acquired, specific transaction in the blockchain network 400, i.e., the distributed database in the blockchain network 400, to thereby complete the issuance, at a step of S230.

Also, the auditors of the certificates who are related to the government institutions may request, an audit via a verification-requesting device 500 to confirm whether the information related to the specific certificate issued in accordance with the present disclosure is forged.

For this purpose, the issuance-requesting server 200 may determine whether the verification-requesting device 500 requested monitoring of the specific certificate, at a step of S251, and if the monitoring is determined to have been requested, the issuance-requesting server 200 may retrieve the specific identification information of the specific user whose specific certificate is the subject of the requested monitoring from the DB 211 for user identification, and may transmit the specific identification information to the certificate-managing server 300, at a step of S252.

Then, the certificate-managing server 300 may confirm a presence of the specific node index information on the specific user in the DB 311 for registration information by referring to the specific identification information on the specific user whose specific certificate is the subject of the requested monitoring.

If the specific node index information on the specific user is determined as present in the DB 311 for registration information, then the certificate-managing server 300 may directly enter a step of S257 described later, where the specific root hash value for comparison is generated.

Then, if the specific node index information on the specific user does not exist, the certificate-managing server 300 may instruct the third hashing engine 320 to hash the certificates matching the identification information stored sequentially in the DB 311 for registration information that do not correspond, to any node index information, to thereby generate each of hash values of each of the certificates.

And if the specific node index information on the specific user is determined, as present, the certificate-managing server 300 may instruct the third hashing engine 320 to hash ail of the certificates corresponding to the specific root hash identification information, to thereby generate hash values for comparison by referring to specific root hash identification information corresponding to the specific identification information on the specific user and apply the Merkle tree operation to each of the leaf nodes, to thereby generate the specific root hash value for comparison by referring to specific node index information including each of the hash values for comparison, at a step of S257. That is, the certificate-managing server 300 may apply the Merkle tree operation to each of the leaf nodes including each of the hash values for comparison of each of the certificates corresponding to the specific root hash identification information, to thereby generate the specific root hash value for comparison, by referring to the specific root hash identification information, corresponding to the specific identification information on the specific user.

Thereafter, the certificate-managing server 300 may acquire the specific transaction ID, by referring to the specific root hash identification information corresponding to the specific identification information on the specific user and may transmit the specific transaction ID to the blockchain network 400 comprised of the blockchain nodes 410, at a step of S258.

Thereafter, at least one of the blockchain nodes 410 among the blockchain network 400 may retrieve the specific transaction from the blockchain network 400, i.e., the distributed database by referring to the specific transaction ID, may extract the specific roof hash value for reference included in the retrieved specific transaction, and may transmit the specific root hash value for reference to the certificate-managing server 300, at a step of S259.

Thereafter, the certificate-managing server 300 may acquire the specific root hash value for reference, and may compare the specific root hash value for reference with the specific root hash value for comparison, to thereby determine whether the two hash values are identical to each other, at a step of S260.

That is, if a request for verification of the specific certificate including the specific identification information on the specific user is acquired, the certificate-managing server 300 may perform (i) a process of generating the specific root hash value for comparison by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values for comparison of each of the certificates corresponding to the specific root hash identification information, by referring to the specific root hash identification information corresponding to the specific identification information on the specific user, (ii) one of (ii-1) a process of retrieving from the distributed database the specific root hash value, as the specific root hash value for reference, included in the specific transaction corresponding to the specific transaction ID related, to the specific root hash identification information, and (ii-2) a process of instructing at least one of the blockchain nodes 410 in the blockchain network 400 to retrieve from the distributed database the specific root hash value for reference included in the specific transaction corresponding to the specific transaction ID; and (iii) a process of confirming a validity of the specific certificate by referring to the specific root hash value for comparison and the specific root hash value for reference.

On the other hand, if the specific root hash value for comparison and the specific root hash value for reference are determined as identical, the certificate-managing server 300 may allow a message, representing that the specific certificate is not forged, to be transmitted to the verification-requesting device 500, at a step of S261.

Then, if the specific root hash value for reference and the specific root hash value for comparison are not identical to each other, then the certificate-managing server 300 may compare, for all the leaf nodes, (i) each of hash values of each of the certificates in each of the leaf nodes used to calculate the specific root hash value for reference corresponding to the specific hash value for reference, and (ii) its corresponding each of hash values of each of the certificates in each of the leaf nodes used to calculate the specific root hash value for comparison corresponding to the specific hash value for comparison, and identify one or more certain leaf nodes, which have different hash values with each other, among ail the leaf nodes, at a step of S262.

Then, after recognizing the specific node index information corresponding to the specific certificate at the step of S262, the certificate-managing server 300 may confirm whether one of the certain leaf nodes with the different hash values is the leaf node corresponding to the specific user, at a step of S263.

If the leaf node with the different hash value is the leaf node corresponding to the specific user, the certificate-managing server 300 may allow a message, representing that the specific certificate for comparison of the specific user is forged, to be transmitted to the verification-requesting device 500, at a step of S264.

Also, if any one of the certain leaf nodes with the different hash values is not the leaf node corresponding to the specific user, the certificate-managing server 300 may allow a message, representing that the specific certificate for comparison of the specific user is not forged, to be transmitted to the verification-requesting device 500, at a step of S265.

That is, if the specific root hash value for comparison and the specific root hash value for reference are not identical to each other, the certificate-managing server 300 may compare (i) each of the hash values for reference, corresponding to each user, in leaf nodes among the leaf nodes corresponding to the specific root hash value for reference and (ii) each of the hash values for comparison in leaf nodes among the leaf nodes corresponding to the specific root hash value for comparison, to thereby determine whether the specific certificate is valid.

Thereafter, the certificate-managing server 300 may determine at least one of the certificates, corresponding to the specific root hash value of leaf nodes related to the specific node index information of the specific certificate among the certificates stored in the DB 311 for registration information, is forged, and may handle the forgery.

Although the issuance-requesting server 200 and the certificate-managing server 300 are described as linked with each, other to issue the specific certificate based on the blockchain network in the above description, a single server, i.e., the authentication-supporting server 2000, may function as the issuance-requesting server 200 and the certificate-managing server 300 and may issue the specific certificate based on the blockchain network, as described below. In the description below, the part easily deducible from the method for issuing the specific certificate based on the blockchain network by using the issuance-requesting server 200 and the certificate-managing server 300 will be omitted.

First, if the personal information on the specific user for issuing the specific certificate is acquired, from the specific user device 100 at the step of S100, the authentication-supporting server 20 00 may request the public key of the specific, user from the specific user device 100 at the step of S110, to thereby instruct the specific user device 100 to generate the private key and the public key of the specific user and transmit the public key to the authentication-supporting server 2000 at the steps of S120 and S130.

Then, if the public key is acquired, the authentication-supporting server 2000 may store the specific certificate, including at least the public key of the specific user, such that the specific certificate matches the specific identification information corresponding to the specific personal information on the specific user at the step of S140, and may monitor whether one of the current anchoring conditions to register the specific transaction in the blockchain network 400 is satisfied at the step of S150.

Thereafter, if said one of the current anchoring conditions is satisfied, the authentication-supporting server 2000 may perform a process of generating the specific root hash value for reference by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates stored after the latest previous anchoring condition is satisfied. Herein, the authentication-supporting server 2000 may generate and manage information related to the Merkle tree operation, like information on each of the certificates corresponding to each of the leaf nodes, and each of the hash values in each of the leaf nodes, at the step of S210.

Then, the authentication-supporting server 2000 may perform (i) one of (i-1) a process of storing the specific transaction including the specific root hash value for reference in the distributed database on the blockchain network 400, and (i-2) a process of instructing at least one of the blockchain nodes 410 in the blockchain network 400 to store the specific transaction in the distributed database, at the step of S220 and (ii) a process of acquiring a specific transaction ID representing a location of the specific transaction on the distributed database, at the step of S230.

If said one of the current anchoring conditions is satisfied, the authentication-supporting server 2000 may perform ii) one of (i-1) a process of retrieving from the distributed database each of previous root hash values for reference included in each of previous transactions corresponding to each of previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, and (i-2) a process of instructing the at least one of the blockchain nodes 410 on the blockchain network 400 to retrieve from the distributed database each of the previous root hash values for reference included in each of the previous transactions corresponding to each of the previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, at the steps of S160, S170, and S180.

Then, the authentication-supporting server 2000 may acquire each of the previous certificates corresponding to each of the previous root hash values for reference, and may apply the Merkle tree operation to each of the leaf nodes including each of the previous hash values for comparison of each of the previous certificates, to thereby generate the previous root hash values for comparison at the step of S190, and may compare each of the previous root hash values for reference and each of the previous root hash values for comparison, to thereby determine whether the previous certificates are valid, at the step of S200.

Herein, if one of the previous root hash values for reference is determined as different from its corresponding previous root hash value for comparison, the authentication-supporting server 2000 may determine that at least one of the previous certificates corresponding to said corresponding previous root hash value for comparison is forged at the step of S201.

Also, if a request for verification of the specific certificate including specific identification information on the specific user is acquired at a step of S251, the authentication-supporting server 2000 may apply the Merkle tree operation to each of the leaf nodes including each of the hash values for comparison of each of the certificates corresponding to the specific root hash identification information, to thereby generate the specific root hash value for comparison, by referring to specific root hash identification information corresponding to the specific identification information on the specific user, at a step of

Then, the authentication-supporting server 2000 may perform (i) one of (i-1) a process of retrieving from the distributed database the specific root hash value for reference included in the specific transaction corresponding to the specific transaction ID, by referring to the specific transaction ID and (i-2) a process of instructing the at least one of the blockchain nodes on the blockchain network to retrieve from the distributed database the specific root hash value for reference included in the specific transaction corresponding to the specific transaction ID, at the steps of S258 and S259.

Thereafter, the authentication-supporting server 2000 may compare the specific root hash value for reference and the specific root hash value for comparison at the step of S260, to thereby determine whether the specific certificate is valid, at the step of S261.

Herein, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, the authentication-supporting server 2000 may compare (i) each of hash values for reference included in each of the leaf nodes corresponding to the specific root hash value for reference, and (ii) each of hash values for comparison included in each of the leaf nodes corresponding to the specific root hash value for comparison, at the steps of S262 and S263 to thereby determine at least one forged certificate, among the certificates, corresponding to the specific root hash identification information at the steps of S264, S265, and S266.

That is, if the specific root hash value for reference and the specific root hash value for comparison are not identical to each other, the certificate-managing server 2000 may compare (i) each of the hash values for reference, corresponding to each user, in one of the leaf nodes corresponding to the specific root hash value for reference and (ii) each of the hash values for comparison in one of the leaf nodes corresponding to the specific root hash value for comparison, to thereby determine whether the specific

FIGS. 9 to 16 illustrate a method and a system for authenticating the specific certificate based on the blockchain network.

As illustrated, a system for authenticating the specific certificate based on the blockchain network in accordance with the present disclosure may include the specific user device 100, an issuance-requesting server 600, the certificate-managing server 300, the blockchain network 400, and the verification-requesting device 500.

The authentication-requesting server 600 may include a random number generator 630 and a second encrypting engine 640, and may relay a request for an authentication based on the blockchain network by transmitting the specific identification information for the issuance of the specific certificate on the specific user who operates the specific user device 100, in response to the request for the authentication from the specific user device 100.

For this purpose, the authentication-requesting server 600 may include a third DB part 610.

The third DB part 610 may store the specific identification information on the specific user who operates the specific user device 100, and may further include a DB 611 for user identification which stores personal information corresponding to the specific identification information on the specific, user used at a time of the issuance. Herein, the specific identification information on the specific user may be information generated by hashing the personal information on the specific user.

Based on the specific identification information on the specific user transmitted from the authentication-requesting server 600, if the specific certificate is determined as valid, the certificate-managing server 300 may transmit the public key of the specific user to the authentication-requesting server 600.

To perform such functions, the certificate-managing server 300 may include the second DB part 310 and the third hashing engine 320.

First, the second DB part 310 may include the DB 311 for registration information where all of the certificates, all pieces of root hash identification information used for identifying all of the root hash values, and all pieces of node index information, as corresponding to the all pieces of identification information, including (i) each of the hash values corresponding to each of the leaf nodes used for the Merkle tree operation of the root hash values, and (ii) the identification information on each of the users corresponding to each of the leaf nodes, are stored and may include the DB 312 for monitoring forgery where all of the transaction IDs, generated as identifiers every time all of the transactions are created at the certificate-managing server 300, are stored such that each of ail of the transaction IDs corresponds to each of all of the root hash values.

Based on this, a process of the certificate-managing server 300 determining whether the specific certificate is valid by referring to the transmitted specific identification information is described as follows.

First, the certificate-managing server 300 may retrieve the specific certificate of the specific user from the DB 311 for registration information by referring to the specific identification information on the specific user transmitted from the authentication-requesting server 600 and may instruct the third hashing engine 320 to hash the specific certificate, to thereby generate the specific hash value for comparison of the specific, certificate.

Thereafter, the certificate-managing server 300 may retrieve the specific node index information from the DB 311 for registration information, may acquire the specific hash value for reference in the leaf node corresponding to the specific certificate.

Thereafter, the certificate-managing server 300 may compare the specific hash value for reference with the specific hash value for comparison, and if the two hash values are determined as identical to each other, may determine that the specific certificate is valid.

If the specific hash value for reference and the specific hash value for comparison are determined as not identical to each other, the certificate-managing server 300 may allow a message, representing that the authentication based on the blockchain network is refused, to be transmitted to the specific user device 100.

By these processes, damages to the legitimate users may be minimized by allowing the users to quickly recognize and respond to forgery and preventing illegal use by illegal, users via hacking.

Meanwhile, if the specific hash value for reference and the specific hash value for comparison are determined as identical to each other, the certificate-managing server 300 may further retrieve from the DB 311 for registration information the specific root, hash identification information which is an identifier for the specific root hash value corresponding to the specific certificate of the specific user.

Thereafter, the certificate-managing server 300 may retrieve from the DB 311 for registration information all of the certificates, corresponding to the specific root hash value for reference, including the specific certificate of the specific user, that is, all of the certificates corresponding to the leaf nodes used for the Merkle tree operation of the specific root hash value for reference, by referring to the retrieved specific root hash identification information, and may instruct the third hashing engine 320 to apply the Merkle tree operation to each of the leaf nodes including each of the hash values for comparison of ail of the retrieved certificates, to thereby generate the specific root hash value for comparison, in addition, the certificate-managing server 300 may retrieve a specific transaction ID from the DB 312 for monitoring forgery by referring to the retrieved specific root hash identification information, and may transmit the specific transaction ID to the blockchain network 400 comprised of the blockchain nodes 410.

Thereafter, at least one of the blockchain nodes 410 on the blockchain network 400 may retrieve the specific transaction from the blockchain network 400, i.e., the distributed database by referring to the specific transaction ID, may extract the specific roof hash value for reference included in the retrieved specific transaction, and may transmit the specific root hash value for reference to the certificate-managing server 300.

The certificate-managing server 300 may acquire the specific root hash value for reference, and may compare the acquired specific root hash value for reference with the created specific root hash value for comparison, and if the two hash values are identical, may determine that the specific certificate is legitimate.

Also, if the specific root hash value for reference and the specific root hash value for comparison are not identical, the certificate-managing server 300 may determine that at least one of all of the certificates corresponding to the specific root hash value for comparison is forged, and may perform processes of handling the forgery.

By these processes, the present disclosure provides a method of monitoring forgery of information related to registration of the issued certificate of the user in the certificate-managing server 300 every time the authentication based, on the blockchain is requested., and of enabling the user to quickly recognise and respond to the forgery of information related to the registration stored in the certificate-managing server 300.

Thereafter, if the specific certificate is determined as valid and the certificate-managing server 300 transmits a validity-confirming signal including the public key of the specific user, the authentication-requesting server 600 may acquire the validity-confirming signal including the public key and determine whether a protocol used for Internet communications between the specific user devices 100 is HTTP or HTTPS.

Herein, the protocol is used for transfer of hypertext documents between a web server and an Internet browser of a user on the Internet, and includes HTTP (Hypertext Transfer Protocol) and HTTPS (Hypertext Transfer Protocol over Secure Socket Layer) whose difference is whether the documents being transferred are encrypted. That is, the documents are transmitted as plain text in HTTP, and as encrypted text in HTTPS.

Thus, the usage environment of HTTP is vulnerable to hacking, as documents are transferred in plain text.

To resolve the risk of hacking and to authenticate the specific user as a legitimate user of the specific certificate, the authentication-requesting server 600 may instruct the random, number generator 630 to generate a random session key if the protocol between the user devices 100 is HTTP.

Thereafter, the authentication-requesting server 600 may instruct the second encrypting engine 640 to encrypt the random session key by using the public key included in the validity-confirming signal, to thereby acquire and transmit an encrypted random session key to the specific user device 100.

The specific user device 100 may instruct, the first decrypting engine 160 to decrypt the encrypted random session key by using the private key stored in the memory 120, to acquire the random session key, and perform the authentication of the specific user as the legitimate user.

That is, if the specific user device 100 of the specific user does not have the private key, the decryption cannot be performed and thus the specific user cannot be verified as the legitimate user.

In addition, in the usage environment of HTTP, because the documents are transmitted over a secure communication line between the specific user device 100 and the authentication-requesting server 600 using encryption based on the random session key provided by the specific user device 100, the leakage of the private key is prevented, even after the user authentication, and the secure authentication based on the blockchain network is performed.

On the other hand, if the protocol is HTTPS, the documents transferred over a communication line between the specific user device 100 and the authentication-requesting server 600 are already encrypted, therefore only thing required is the user authentication.

For this purpose, if the protocol used between the user devices 100 is determined as HTTPS, the authentication-requesting server 600 may instruct the random number generator 630 to generate nonce data and transmit the nonce data to the specific user device 100.

The specific user device 100 may instruct the first hashing engine 140 to generate nonce data hash information for authentication by hashing the nonce data.

Thereafter, the specific user device 100 may instruct the first encrypting engine 130 to generate encrypted, nonce data hash information for authentication by using the private key of the specific user stored in the memory 120, and transmit the encrypted nonce data hash information for authentication to the authentication-requesting server 600.

The authentication-requesting server 600 may instruct a fourth hashing engine 620 to hash the nonce data, which have been transmitted to the specific user device 100, to thereby generate nonce data hash information for comparison.

Thereafter, the authentication-requesting server 600 may instruct a second decrypting engine 650 to decrypt the encrypted nonce data hash information for authentication by using the public key of the specific user, to thereby generate the nonce data hash information for authentication, and may confirm if the nonce data hash information for authentication corresponds to the nonce data hash information for comparison, to thereby perform the authentication of the specific user.

Meanwhile, the user may revoke the issued certificate based on the blockchain.

For this purpose, if a request for revocation of the specific certificate is received from the specific user device 100, the certificate-managing server 300 may store the specific certificate to be revoked in the DB 311 for registration information such that the specific certificate to be revoked corresponds to the specific identification information on the specific user, and may monitor whether one of the current anchoring conditions is satisfied.

Thereafter, if said one of the current anchoring conditions is satisfied, the certificate-managing server 300 may perform a process of generating the specific root hash value for reference by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates, including the specific certificate to be revoked, stored after the latest previous anchoring condition is satisfied. Herein, the certificate-managing server 30 0 may generate the specific root, hash identification information used for identifying the specific root hash value for reference, and the Merkle tree information on the root hash values, i.e., specific node index information which includes (i) each of the hash values corresponding to each of the leaf nodes used for the Merkle tree operation of the specific root hash value for reference, and iii) the identification information on each of the users corresponding to each of the leaf nodes.

Thereafter, the certificate-managing server 300 may generate (i) the specific transaction including the specific root hash value for reference and (ii) the specific transaction ID used as a key value to search for the specific transaction, and transmit the specific transaction to the blockchain network 400 comprised of the blockchain nodes 410.

Herein, on condition that the certain previous root hash value for reference, created right before said one of the current anchoring conditions is satisfied, has been stored in a predetermined leaf node among leaf nodes corresponding to the specific root hash value for reference to be generated and including a hash value of the specific certificate to be revoked, the certificate-managing server 300 may apply the Merkle tree operation to- each of the leaf nodes, one of which includes the certain previous root hash value for reference, to thereby generate the specific root hash value for reference. That is, one of the leaf nodes may include the certain previous root hash value for reference created right before said one of the current anchoring conditions is satisfied.

At least one of the blockchain nodes 410 in the blockchain network 400 may store the received specific transaction in the blockchain network 400, i.e., the distributed database in the blockchain nodes 410, to thereby complete the revocation of the specific certificate to be revoked.

Also, the auditors of the certificates who are related to the government institutions may request an audit via the verification-requesting device 500 to confirm whether the information related to the certificates, used by the specific user in accordance with the present disclosure, is forged.

In order to do so, the third DE part 610 of the authentication-requesting server 600 may include the DB 611 for user identification which stores the specific personal information on the specific user who operates the specific user device 100.

Also, the DB 311 for registration information of the certificate-managing server 300 may store the certificates including the specific certificate to be revoked, the specific root hash identification information used for identifying the specific root hash value for reference, and the specific node index information, as corresponding to the specific identification information, including (i) each of the hash values, including the hash value of the specific certificate to be revoked, corresponding to each of the leaf nodes used for the Merkle tree operation of the specific, root hash value for reference, and (ii) the identification information on each of the users corresponding to each of the leaf nodes.

For this purpose, the verification-requesting device 500 may transmit a request for monitoring the specific certificate of the specific user to the issuance-requesting server 600.

The authentication-requesting server 600 may retrieve specific identification information on the specific user who requested, the monitoring of the specific certificate from the DE 611 for user identification, and transmit the specific identification information to the certificate-managing server 300.

The certificate-managing server 300 may retrieve specific node index information on the specific user from the DB 311 for registration information by referring to the specific identification information on the specific user who requested the monitoring, and may retrieve specific root hash identification information corresponding to the specific user from the DB 311 for registration information.

Thereafter, the certificate-managing server 300 may instruct the third hashing engine 320 to hash ail of the certificates, including the specific certificate to be revoked, corresponding to the specific root hash identification information, to thereby generate each of the hash values for comparison of each of the certificates by referring to the specific root hash identification information corresponding to the specific identification information on the specific user, and apply the Merkle tree operation to each of the leaf nodes including each of the hash values for comparison, having the hash value of the specific certificate to be revoked, to thereby generate the specific root hash value for comparison by referring to the specific node index information including each of the hash values for comparison, having the hash value of the specific certificate to be revoked. That is, the certificate-managing server 300 may apply the Merkle tree operation to each of the leaf nodes including each of the hash values for comparison of each of the certificates, including the specific certificate to be revoked, corresponding to the specific root hash identification information, to thereby generate the specific root hash value for comparison, by referring to the specific root hash identification information corresponding to the specific identification information on the specific user.

Also, the certificate-managing server 300 may retrieve the specific transaction ID from, the DB 312 for monitoring forgery by referring to the specific root hash identification information corresponding to the specific identification information on the specific user and may transmit the specific transaction ID to the blockchain network 400 comprised of the blockchain nodes 410.

Thereafter, at least one of the blockchain nodes 410 on the blockchain network 400 may retrieve the specific transaction from the blockchain network 400, i.e., the distributed database by referring to the specific transaction ID, and may extract the specific root hash value for reference included in the retrieved specific transaction, and may transmit the specific root hash value for reference to the certificate-managing server 300.

If the specific root hash value for comparison and the transmitted specific root hash value for reference are determined as identical, the certificate-managing server 300 may allow a message, representing that the specific certificate of the specific user is not forged, to be transmitted to the verification-requesting device 500.

On the other hand, if the transmitted specific root hash value for reference and the specific root hash value for comparison are not identical to each other, then the certificate-managing server 300 may compare, for ail the leaf nodes, (i) each of hash values of each of the certificates, including the specific certificate to be revoked, in each of the leaf nodes used to calculate the specific root hash value for reference corresponding to the specific hash value for reference, and (ii) its corresponding each of hash values of each of the certificates, including the specific certificate to be revoked, in each of the leaf nodes used to calculate the specific root hash value for comparison corresponding to the specific hash value for comparison, and identify one or more certain leaf nodes, which have different hash values with each other, among ail the leaf nodes.

Thereafter, if one of the leaf nodes, which includes one of the different hash values of the specific certificate or one of the different hash values of the specific certificate to be revoked, corresponds to the leaf node of the specific certificate of the specific user, the certificate-managing server 300 may allow a message, representing the specific certificate of the specific user is forged, to be transmitted to the verification-requesting device 500.

Also, if the leaf node including the different hash value of the specific certificate does not correspond to the leaf node of the specific certificate of the specific user, the certificate-managing server 300 may allow a message, representing the specific certificate of the specific user is not forged, to be transmitted to the verification-requesting device 500. Then, the certificate-managing server 300 may determine that at least one of ail of the certificates, which include the specific certificate to be revoked, corresponding to the specific root hash value for comparison, as forged, and may perform, processes of handling the forgery.

Although the authentication-requesting server 600 and the certificate-managing server 300 are described as separate devices in the above description, a single server, i.e., the authentication-supporting server 2000, may function as the authentication-requesting server 600 and the certificate-managing server 300.

That is, the authentication-supporting server 2 000 may perform the authentication based on the blockchain network and may include a communication part (not illustrated)and a processor (not illustrated). Identical reference numerals are for convenience of explanation but not intended for representing sameness of separate devices. Further, according to another example embodiment of the present disclosure, the method may be performed by the authentication-supporting server 2000 or another server of a different configuration. Further, the authentication-supporting server 2000 may be servers corresponding to each of nodes of the blockchain network 400, or maybe a server managing each of the node of the blockchain network 4 00, or may be a transaction server.

Specifically, the authentication-supporting server 2000 typically achieves desired system performance by using combinations of at least one computing device and at least one computer software, e.g., a computer processor, a memory, a storage, an input device, an output device, or any other conventional computing components, an electronic communication storage system such as a network-attached, storage (NAS) device and a storage area network (SAN) as the computing device and any instructions that allow the computing device to function in a specific way as the computer software.

The communication part of such devices may transmit requests to and receive responses from other linked devices. As one example, such requests and responses may be carried out by the same TCP session, but the scope of the present disclosure is not limited thereto. For example, they could be transmitted and received as UDP datagrams.

Also, the processor of such, devices may include hardware configuration of MPU (Micro Processing Unit) or CPU (Central Processing Unit), cache memory, data bus, etc. Additionally, OS and software configuration of applications that achieve specific purposes may be further included.

A process of the authentication of the specific certificate based on the blockchain network by using the system for authenticating the specific certificate based on the blockchain network in accordance with the present disclosure is described as follows.

The specific user may transmit an authentication request for the specific certificate based on the blockchain network by connecting to the authentication-requesting server 600 by using the specific user device 100, at a step of S300.

The authentication-requesting server 600 may retrieve the specific identification information on the specific user from the DB 611 for user identification, in response to the authentication request from the specific user, and may transmit the specific identification information to the certificate-managing server 300, at a step of S310.

The certificate-managing server 300 may determine whether the specific certificate of the specific user is valid by referring to the transmitted specific identification information at a step of S320. First, the certificate-managing server 300 may retrieve the specific certificate of the specific user from the DB 311 for registration information by referring to the specific identification information on the specific user transmitted from the authentication-requesting server 600, may instruct the third hashing engine 320 to hash the specific certificate, to thereby generate the specific hash value for comparison, may retrieve the specific node index information from the DB 311 for registration information by referring to the specific identification information on the specific user, and may acquire the specific hash value for reference in the leaf node corresponding to the specific certificate, at a step of S321.

Then, the certificate-managing server 300 may compare the acquired specific hash value for reference with the specific hash value for comparison, and may determine if the two hash values are identical to each other, at a step of S322.

Herein, if the specific hash value for reference and the specific hash value for comparison are determined as not identical to each other, the certificate-managing server 300 may allow a message, representing that the authentication based, on the blockchain network is refused, to be transmitted to the specific user device 100.

On the other hand, if the specific hash value for reference and the specific hash value for comparison are determined as identical to each other, the certificate-managing server 300 may further retrieve from the DB 311 for registration information the specific root hash identification information which is an identifier for the specific root hash value for reference corresponding to the specific certificate of the specific user.

Thereafter, the certificate-managing server 300 may retrieve, from the DB 311 for registration information, all of the certificates, corresponding to the specific root hash value for reference, including the specific certificate of the specific user, that is, all of the certificates corresponding to each of the leaf nodes used for the Merkle tree operation of the specific root hash value for reference, by referring to the retrieved specific roof hash identification information, and may instruct the third hashing engine 320 to apply the Merkle tree operation to each of the leaf nodes including each of the hash values for comparison of all of the retrieved certificates, to thereby generate the specific root hash value for comparison at a step of S325.

Thereafter, the certificate-managing server 300 may retrieve the specific transaction ID from the DB 312 for monitoring forgery by referring to the retrieved specific root hash identification information, and may transmit the specific transaction ID to the blockchain network 400 comprised of the blockchain nodes 410 at a step of S326.

Thereafter, at least one of the blockchain nodes 410 on the blockchain network 400 may retrieve the specific transaction from the blockchain network 400, i.e., the distributed database by referring to the specific transaction ID, may extract the specific root hash value for reference included in the retrieved specific transaction, and may transmit the specific root hash value for reference to the certificate-managing server 300 at a step of S327.

Thereafter, the certificate-managing server 300 may receive the specific root hash value for reference, and may compare the specific root hash value for reference with the specific root hash value for comparison, to thereby determine whether the two hash values are identical to each other, at a step of S328.

Herein, if the specific root hash value for reference and the specific root hash value for comparison are determined as not identical, the certificate-managing server 300 may determine that at least one of ail of the certificates, corresponding to the specific roof hash value for comparison, as forged at a step of S329, and may perform processes of handling the forgery.

On the other hand, if the specific root hash value for reference and the specific root hash value for comparison are determined as identical, the certificate-managing server 300 may determine that the specific certificate is legitimate.

Thus, the certificate-managing server 300 may retrieve the public hey of the specific user from the DB 311 for registration information by referring to the specific identification information on the specific user, and may transmit the public key to the authentication-requesting server 600, at a step of S330.

The authentication-requesting server 600 may acquire the public key and authenticate the specific user of the specific user device 100 based on the acquired public key, at a step of S340 as follows.

First, the authentication-requesting server 600 may determine whether the protocol used for Internet communications of the specific user device 100 requesting the authentication is HTTP or HTTPS, at a step of S340.

If the protocol between the specific user devices 100 is HTTP, the authentication-requesting server 600 may instruct the random number generator 630 to generate a random session key, at a step of 3350.

Then, the authentication-requesting server 600 may instruct the second encrypting engine 640 to encrypt the random session key by using the public key of the specific user, to thereby generate and transmit an encrypted random session key to the specific user device 100, at a step of S360.

The specific user device 100 may acquire the encrypted random session key, instruct the first decrypting engine 160 to decrypt the encrypted random session key by using the private key of the specific user stored in the memory 120, and to acquire the random session key, and may complete the authentication of the specific user, at a step of 3370,

Then, if the protocol of the specific user device 100 requesting the authentication is HTTPS, the authentication-requesting server 600 may instruct the random number generator 630 to generate nonce data and transmit the nonce data to the specific user device 100, at a step of S330.

The specific user device 100 may instruct the first hashing engine 140 to generate nonce data hash information for authentication by hashing the nonce data, at a step of S390.

Thereafter, the specific user device 100 may instruct the first encrypting engine 130 to acquire encrypted nonce data hash information for authentication by using the private key of the specific user stored in the memory 120, and transmit the encrypted nonce data hash information for authentication to the authentication-requesting server 600, at a step of S400.

The authentication-requesting server 600 may instruct the fourth hashing engine 620 to hash the nonce data, which have been transmitted to the specific user device 100, to acquire nonce data hash information for comparison, may instruct the second decrypting engine 650 to decrypt the encrypted nonce data hash information for authentication by using the public key of the specific user to acquire the nonce data hash information for authentication, and may confirm if the nonce data hash information for authentication is identical to the nonce data hash information, for comparison, to thereby perform the authentication of the specific user, at a step of S410.

Meanwhile, the user may revoke the issued certificate based on the blockchain.

For this purpose, the certificate-managing server 300 may determine if a request for revocation of a specific certificate to be revoked is acquired from the specific user device 100 at a step of S500, and if the request is acquired, may store the specific certificate to be revoked in the DB 311 for registration information such that the specific certificate to be revoked corresponds to the specific identification information on the specific user at a step of 3510, and may monitor whether one of the current anchoring

Then, if said one of the current anchoring conditions is satisfied, the certificate-managing server 300 may perform a process of generating the specific root hash value for reference by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates, including the specific certificate to be revoked, stored after the latest previous anchoring condition is satisfied. Herein, the certificate-managing server 300 may generate ail pieces of the root hash identification information used for identifying all of the root hash values, and the Merkle tree information on all of the root hash values, i.e., all pieces of node index information which include (i) each of the hash values corresponding to each of the leaf nodes used for the Merkle tree operation of ail of the roof hash values, and (ii) all of the identification information on each of the users corresponding to each of the leaf nodes.

Thereafter, the certificate-managing server 300 may generate (i) the transaction including the root hash values and (ii) the transaction ID used as a key value to search the transaction, and transmit the transaction to the blockchain network 400 comprised of the blockchain nodes 410.

Herein, on condition that the certain previous root hash value for reference, created right before said one of the current anchoring conditions is satisfied, has been stored in a predetermined leaf node among leaf nodes corresponding to the specific root hash value for reference to be generated and including a hash value of the specific certificate to be revoked, the certificate-managing server 300 may apply the Merkle tree operation to each of the leaf nodes, one of which includes the certain previous root hash values for reference, to thereby generate the specific root hash value for reference. That is, one of the leaf nodes may include the certain previous of the current anchoring conditions is satisfied.

At least one of the blockchain nodes 410 in the blockchain network 400 may store the acquired specific transaction in the blockchain network 400, i.e., the distributed database in the blockchain nodes 410 at a step of S530, to thereby complete the revocation.

As a result, the specific user may be allowed to confirm the revocation of the specific certificate to be revoked.

Further, the auditors who audit an individual user or verification-requesting device 500 to confirm whether information related to the specific certificate is forged.

That is, the authentication-requesting server 600 may determine whether the verification-requesting device 500 requested, monitoring of the specific certificate at a step of S600, and if the monitoring is determined, as requested, the specific identification information of the specific user whose certificate is the subject of the requested monitoring may be retrieved from the DB 211 for user identification, and the specific identification information may be transmitted to the certificate-managing server 300 at a step of S610.

The certificate-managing server 300 may retrieve specific node index information on the specific user from the DB 311 for registration information by referring to the specific identification information on the specific user who requested the monitoring, and may retrieve the specific root hash identification information corresponding to the specific user from the DB 311 for registration information, at a step of S620.

Thereafter, the certificate-managing server 300 may hash all of the certificates corresponding to the specific root hash identification information by referring to the retrieved specific root hash identification information, to thereby generate the hash values for comparison. Herein, said all of the certificates may include the specific certificate to be revoked. Then, on condition that each of the hash values for comparison has been allocated to each of its corresponding leaf nodes by referring to the specific node index information, the certificate-managing server 300 may instruct the third hashing engine 320 to apply the Merkle tree operation to each of the hash values for comparison, to thereby generate the specific root hash value for comparison at a step of S630. That, is, the certificate-managing server 300 may apply the Merkle tree operation to each of the leaf nodes including each of the hash values for comparison of each of the certificates corresponding to the specific roof hash identification information, to thereby generate the specific root hash value for comparison, by referring to specific root hash identification information corresponding to the specific identification information on the specific user.

Thereafter, the certificate-managing server 300 may retrieve the specific transaction ID from the DB 312 for monitoring forgery by referring to the specific root hash identification information corresponding to the specific identification information on the specific user and may transmit the specific transaction ID to the blockchain network 400 comprised of the blockchain nodes 410, at a step of S640.

At least one of the blockchain nodes 410 on the blockchain network 400 may retrieve the specific transaction from the blockchain network 400, i.e., the distributed database by referring to the specific transaction ID, and may extract the specific root hash value for reference included in the retrieved specific transaction, and may transmit the specific root hash value for reference to the certificate-managing server 300, at a step of S650.

Thereafter, the certificate-managing server 300 may acquire the specific root hash value for reference, and may compare the specific root hash value for reference with the specific root hash value for comparison, to thereby determine whether the two hash values are identical to each other, at a step of S660.

Herein, if the specific root hash value for comparison and the specific root hash value for reference are determined as identical, the certificate-managing server 300 may allow a message, representing that the specific certificate is not forged, to be transmitted to the verification-requesting device 500, at a step of S670.

On the other hand, if the specific root hash value for reference and the specific root hash value for comparison, are not identical to each other, then the certificate-managing server 300 may compare, for all the leaf nodes, (i) each of hash values of each, of the certificates in each, of the leaf nodes used to calculate the specific root hash value for reference corresponding to the specific hash value for reference, and (ii) its corresponding each of hash values of each of the certificates in each of the leaf nodes used to calculate the specific root hash value for comparison corresponding to the specific hash value for comparison, and identify one or more certain leaf nodes, which have different hash values with each other, among all the leaf nodes, at a step of S661.

Thereafter, the certificate-managing server 300 may determine whether one of the leaf nodes including the different hash value corresponds to the specific certificate of the specific user at a step of SS62, and if said one of the leaf nodes corresponds to the specific certificate, the certificate-managing server 300 may allow a message, representing the specific certificate of the specific user is forged, to be transmitted to the verification-requesting device 500 at a step of S663. Then, the certificate-managing server 300 may determine that at least one of all of the certificates, corresponding to the specific root hash value for comparison, as forged at a step of SS65, and may perform processes of handling the forgery.

Also, if the leaf node including the different hash value does not correspond to the specific user, the certificate-managing server 300 may allow a message, representing the specific certificate of the specific user is not forged, to foe transmitted to the verification-requesting device 500 at a step of S664.

Although the issuance-requesting server 200 and the certificate-managing server 300 are described as linked with each other to perform the authentication based on the blockchain network in the above description, a single server, i.e., the authentication-supporting server 2000, may perform the authentication based on the blockchain network.

That is, if the authentication request, including the specific personal information on the specific user, of the specific certificate is acquired at steps of S300 and S310, the authentication-supporting server 2000 may determine whether the specific certificate is valid by referring to the specific identification information on the specific user corresponding to the specific personal information on the specific user at a step of S320, and if the specific certificate is determined as valid, may perform the authentication of the specific user via communication with the specific user device 100 by using the public key corresponding to the specific identification information on the specific user at steps of S330 and S340.

Herein, one can easily understand confirmation of the validity of the certificates, the authentication of the specific user, etc. by referring to the description of the certificate-managing server 300 above.

Also, the authentication-supporting server 2000 may perform the revocation and monitoring of the specific certificate, as the methods mentioned above.

The present disclosure has an effect of reducing a cost to construct the system for issuing the specific certificate which is linked with a top-grade security system to block hacking as much as possible, due to the fact that the public key for the specific certificate, which requires constant maintenance, is saved and managed on the blockchain through a peer-to-peer (P2P) network based, distributed, database instead of being saved and managed on a certificate authority (CA) operating server, of reducing system related costs such as operation and maintenance cost of the constructed system for issuing the specific certificate based on the blockchain network, and of greatly reducing an issuing cost of the specific certificate.

The present disclosure has another effect of grouping the specific user's public keys for the specific certificate as many as the predetermined number, compressing the grouped public keys, and registering transaction information that includes the grouped public keys list in order to minimize the network traffics, to thereby also minimize the network overload while registering the transaction information in the blockchain network, in the process of issuing the specific certificate.

The present disclosure has still another effect of performing an authentication process of the specific certificate based on the blockchain network without exposure of the public key of the specific user when issuing the specific certificate by preventing the specific user's public key from being registered in the blockchain network, and of monitoring forgery and falsification of authentication related information that includes the public key of the specific user.

The embodiments of the present disclosure as explained above can be implemented in a form of executable program command through a variety of computer means recordable to computer readable media. The computer readable media may include solely or in combination, program commands, data files, and data structures. The program commands recorded to the media may be components specially designed for the present disclosure or may be usable to a skilled human in a field of computer software. Computer readable media include magnetic media such as hard disk, floppy disk, and magnetic tape, optical media such as CD-ROM and DVD, magneto-optical media such as floptical disk and hardware devices such as ROM, RAM, and flash memory specially designed to store and carry out program commands, Program commands include not only a machine language code made by a compiler but also a high level code that can be used by an interpreter etc., which is executed by a computer. The aforementioned hardware device can work as more than a software module to perform the action of the present disclosure and they can do the same in the opposite case.

As seen above, the present disclosure has been explained by specific matters such as detailed components, limited embodiments, and drawings. They have been provided only to help more general understanding of the present disclosure. It, however, will be understood by those skilled in the art that various changes and modification may be made from the description without departing from the spirit and scope of the disclosure as defined in the following claims.

Accordingly, the thought of the present disclosure must not be confined to the explained embodiments, and the following patent claims as well as everything including variations equal or equivalent to the patent claims pertain to the category of the thought of the present disclosure. 

What is claimed is:
 1. A method for issuing one or more certificates based on a blockchain network, comprising steps of: (a) an authentication-supporting server, if personal information on a specific user for issuing a specific certificate of the specific user among the certificates is acquired from a user device, performing (i) a process of instructing the user device to generate a public key and a private key of the specific user and transmit the public key to the authentication-supporting server, (ii) a process of storing the specific certificate including the public key such that the specific certificate corresponds to the personal information, and (iii) a process of determining whether one of current anchoring conditions for registering a specific transaction in the blockchain network is satisfied, wherein the current anchoring conditions include one of a condition that a predetermined number of the certificates, including the specific certificate, are stored after a previous anchoring condition is satisfied and a condition that a predetermined time is lapsed after the previous anchoring condition is satisfied; (b) the authentication-supporting server, if said one of the current anchoring conditions is satisfied, performing a process of generating a specific root hash value by applying a Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates stored after the previous anchoring condition is satisfied; and (c) the authentication-supporting server performing (i) one of (i-1) a process of storing the specific transaction including the specific root hash value in a distributed database on the blockchain network, and (i-2) a process of instructing at least one of blockchain nodes in the blockchain network to store the specific transaction in the distributed database, and (ii) a process of acquiring a specific transaction ID representing a location of the specific transaction on the distributed database.
 2. The method of claim 1, further comprising a step of: (d) the authentication-supporting server, if a request for verification of the specific certificate including identification information on the specific user is acquired, performing (i) a process of generating a specific root hash value for comparison by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values for comparison of each of the certificates corresponding to specific root hash identification information, by referring to the specific roof hash identification information corresponding to the specific identification information on the specific user, wherein the specific root hash identification information includes information for identifying a specific root bash value for reference which is the specific root hash value generated at the step of (b); (ii) one of (ii-1) a process of retrieving from the distributed database the specific root hash value, as a specific root hash value for reference, included in the specific transaction corresponding to the specific transaction ID, and (ii-2) a process of instructing at least one of the blockchain nodes to retrieve from the distributed database the specific root hash value for reference included in the specific transaction corresponding to the specific transaction ID; and (iii) a process of confirming a validity of the specific certificate by referring to the specific root hash value for comparison and the specific root hash value for reference.
 3. The method of claim 2, wherein, at the step of (d), the authentication-supporting server, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) a specific hash value for reference included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for reference and (ii) a specific hash value for comparison included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for comparison, to thereby confirm the validity of the specific certificate.
 4. The method of claim 2, wherein, at the step of (d), the authentication-supporting server, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) each of hash values for reference included in each of the leaf nodes corresponding to the specific root hash value for reference, and (ii) each of hash values for comparison included in each of the leaf nodes corresponding to the specific root hash value for comparison, to thereby determine at least one forged certificate, among the certificates, corresponding to the specific root hash identification information.
 5. The method of claim 1, wherein, before the step of (b), the authentication-supporting server, if said one of the current anchoring conditions is satisfied, performs (i) one of (i-1) a process of retrieving from the distributed database each of previous root hash values for reference included in each of previous transactions corresponding to each of previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, and (i-2) a process of instructing the at least one of the blockchain nodes on the blockchain network to retrieve from the distributed database each of the previous root hash values for reference included in each of the previous transactions corresponding to each of the previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, (ii) a process of acquiring each of previous certificates corresponding to each of the previous root hash values for reference, and a process of generating each of previous root hash values for comparison by applying the Merkle tree operation to each of leaf nodes including each of previous hash values for comparison of said each of the previous certificates, and (iii) a process of comparing said, each of the previous root hash values for comparison and said each of the previous roof hash values for reference, to thereby confirm a validity of the previous certificates.
 6. The method of claim 1, wherein, at the step of (b), one of the leaf nodes includes a certain previous root hash value created right before said one of the current anchoring conditions is satisfied.
 7. The method of claim 1, wherein, at the step of (b), the authentication-supporting server manages (i) specific root hash identification information which is information used for identifying the specific root hash value, and (ii) specific node index information which is information on (ii-1) each of locations of each of the leaf nodes including each of the hash values of each of the certificates and (ii-2) each of the hash values of each of the certificates.
 8. A method for issuing one or more certificates based on a blockchain network, comprising steps of: (a) a certificate-managing server, if a registration request including identification information on a specific user and a public key of the specific user is acquired, wherein an issuance-requesting server transmits to a user device a key-generating signal instructing creation of the public key and a private key of the specific user in response to personal information on the specific user transmitted from the user device and wherein the issuance-requesting server generates the registration request by referring to the specific identification information on the specific user corresponding to the personal information and the public key sent from the user device, performing (i) a process of storing a specific certificate including the public key such that the specific certificate corresponds to- the specific identification information on the specific user, and (ii) a process of determining whether at least one of current anchoring conditions for registering a specific transaction in the blockchain network is satisfied, wherein the current anchoring conditions include one of a condition that a predetermined number of the certificates, including the specific certificate, are stored after a previous anchoring condition is satisfied and a condition that a predetermined time is lapsed after the previous anchoring condition is satisfied; (b) the certificate-managing server, if said one of the current anchoring conditions is satisfied, performing a process of generating a specific root hash value by applying a Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates stored after the previous anchoring condition is satisfied; and (c) the certificate-managing server performing (i) one of (i-1) a process of storing the specific transaction including the specific root hash value in a distributed database on the blockchain network, and (i-2) a process of instructing at least one of blockchain nodes in the blockchain network to store the specific transaction in the distributed database, and (ii) a process of acquiring gas specific transaction ID representing a location of the specific transaction on the distributed, database.
 9. The method of claim 8, further comprising a step of: (d) the certificate-managing server, if a request for verification of the specific certificate including identification information on the specific user is acquired, performing (i) a process of generating a specific root hash value for comparison by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values for comparison of each of the certificates corresponding to specific root, hash identification information, by referring to the specific root hash identification information corresponding to the specific identification information on the specific user, wherein the specific root hash identification information includes information for identifying a specific root hash value for reference which is the specific root hash value generated, at the step of (b), (ii) one of (ii-1) a process of retrieving from the distributed database the specific root hash value, as a specific root hash, value for reference, included in the specific transaction corresponding to the specific transaction ID, and (ii-2) a process of instructing at least one of the blockchain nodes to retrieve from the distributed database the specific root, hash value for reference included in the specific, transaction corresponding to the specific transaction ID; and (iii) a process of confirming a validity of the specific certificate by referring to the specific root hash value for comparison and the specific root hash value for reference,
 10. The method of claim 9, wherein, at the step of (d), the certificate-managing server, if the specific root hash value for reference is determined as different, from the specific root hash value for comparison, compares (i) a specific hash value for reference included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific roof hash value for reference and (ii) a specific hash value for comparison included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for comparison, to thereby confirm the validity of the specific certificate.
 11. The method of claim 9, wherein, at the step of (d), the certificate-managing server, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) each of hash values for reference included, in each of the leaf nodes corresponding to the specific root hash value for reference, and (ii) each of hash values for comparison included in each of the leaf nodes corresponding to the specific root hash value for comparison, to thereby determine at least one forged certificate, among the certificates, corresponding to the specific root hash identification information.
 12. The method of claim 8, wherein, before the step of (b), the certificate-managing server, if said one of the current anchoring conditions is satisfied, performs (i) one of (i-1) a process of retrieving from the distributed, database each of previous root hash values for reference included in each of previous transactions corresponding to each of previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, and (i-2) a process of instructing the at least one of the blockchain nodes on the blockchain network to retrieve from the distributed database each of the previous roof bash values for reference included in each of the previous transactions corresponding to each of the previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, (ii) a process of acquiring each of previous certificates corresponding to each of the previous root hash values for reference, and a process of generating each of previous root hash values for comparison by applying the Merkle tree operation to each of leaf nodes including each of previous hash values for comparison of said each of the previous certificates, and (iii) a process of comparing said each of the previous root hash values for comparison and said each of the previous root hash values for reference, to thereby confirm a validity of the previous certificates.
 13. The method, of claim 8, wherein, at the step of (b), one of the leaf nodes includes a certain previous root hash value created right before said one of the current anchoring conditions is satisfied.
 14. The method of claim 8, wherein, at the step of (b), the certificate-managing server manages (i) specific root hash identification information which is information used for identifying the specific root hash value, and (ii) specific node index information which is information on (ii-1) each of locations of each of the leaf nodes including each of the hash values of each of the certificates and (ii-2) each of the hash values of each of the certificates.
 15. An authentication-supporting server for issuing one or more certificates based on a blockchain network, comprising: a communication part for acquiring personal information on a specific user for issuing a specific certificate of the specific user among the certificates from a user device; and a processor for performing (I) a process of instructing the user device to generate a public key and a private key of the specific user and transmit the public key to the authentication-supporting server, (II) a process of storing the specific certificate including the public key such that the specific certificate corresponds to the personal information, and (III) a process of determining whether one of current anchoring conditions for registering a specific transaction in the blockchain network is satisfied, wherein the current anchoring conditions include one of a condition that a predetermined number of the certificates, including the specific certificate, are stored after a previous anchoring condition is satisfied and a condition that a predetermined time is lapsed after the previous anchoring condition is satisfied, (IV) if said one of the current anchoring conditions is satisfied, a process of generating a specific root hash value by applying a Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates stored after the previous anchoring condition is satisfied, (V) one of (V-1) a process of storing the specific transaction including the specific root hash value in a distributed database on the blockchain network, and (V-2) a process of instructing at least one of blockchain nodes in the blockchain network to store the specific transaction in the distributed database, and (VI) a process of acquiring a specific transaction ID representing a location of the specific transaction on the distributed database.
 16. The authentication-supporting server of claim 15, further comprising processes of: (VII) if a request for verification of the specific certificate including identification information on the specific user is acquired, generating a specific root hash value for comparison by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values for comparison of each of the certificates corresponding to specific root hash identification information, by referring to the specific root hash identification information corresponding to the specific identification information on the specific user, wherein the specific root hash identification information includes information for identifying a specific root, hash value for reference which is the specific root hash value generated at the process of (IV), (VIII) one of (VIII-1) retrieving from the distributed database the specific root hash value, as a specific root hash value for reference, included in the specific transaction corresponding to the specific transaction ID, and (VIII-2) instructing at least one of the blockchain nodes to retrieve from the distributed database the specific root hash value for reference included in the specific transaction corresponding to the specific transaction ID, and (IX) confirming a validity of the specific certificate by referring to the specific root hash value for comparison and the specific root hash value for reference.
 17. The authentication-supporting server of claim 16, wherein, at the process of (IX), the processor, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) a specific hash value for reference included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for reference and (ii) a specific hash value for comparison included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for comparison, to thereby confirm the validity of the specific certificate.
 18. The authentication-supporting server of claim 16, wherein, at the process of (IX), the processor, if the specific root hash value for reference is determined as different from the specific roof hash value for comparison, compares (i) each of hash values for reference included in each of the leaf nodes corresponding to the specific root hash value for reference, and (ii) each of hash values for comparison included in each of the leaf nodes corresponding to the specific root hash value for comparison, to thereby determine at least one forged certificate, among the certificates, corresponding to the specific root hash identification information.
 19. The authentication-supporting server of claim 15, wherein, before the process of (IV), the processor, if said one of the current anchoring conditions is satisfied, performs (i) one of (i-1) a process of retrieving from the distributed database each of previous transactions corresponding to each of previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, and (i-2) a process of instructing the at least one of the blockchain nodes on the blockchain network to retrieve from the distributed database each of the previous roof hash values for reference included in each of the previous transactions corresponding to each of the previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, (ii) a process of acquiring each of previous certificates corresponding to each of the previous root bash values for reference, and a process of generating each of previous root hash values for comparison by applying the Merkle tree operation to each of leaf nodes including each of previous hash values for comparison of said each of the previous certificates, and (iii) a process of comparing said each of the previous root hash values for comparison and said each of the previous root hash values for reference, to thereby confirm a validity of the previous certificates.
 20. The authentication-supporting server of claim 15, wherein, at the process of (IV), one of the leaf nodes includes a certain previous root hash value created right before said one of the current anchoring conditions is satisfied.
 21. The authentication-supporting server of claim 15, wherein, at the process of (IV), the processor manages (i) specific root hash identification information which is information used for identifying the specific root hash value, and (ii) specific node index information which is information on (ii-1) each of locations of each of the leaf nodes including each of the hash values of each of the certificates and (ii-2) each of the hash values of each of the certificates,
 22. A certificate-managing server for issuing one or more certificates based on a blockchain network, comprising: a communication part for acquiring a registration request including identification information on a specific user and a public key of the specific user, wherein an issuance-requesting server transmits to a user device a key-generating signal instructing creation of the public key and a private key of the specific user in response to personal information on the specific user transmitted from the user device and wherein the issuance-requesting server generates the registration request by referring to the specific identification information on the specific, user corresponding to the personal information and the public key sent, from the user device; and a processor for performing (I) a process of storing a specific certificate including the public key such that the specific certificate corresponds to the specific identification information on the specific user, and (II) a process of determining whether at least one of current anchoring conditions for registering a specific transaction in the blockchain network is satisfied, wherein the current anchoring conditions include one of a condition that a predetermined number of the certificates, including the specific certificate, are stored after a previous anchoring condition is satisfied and a condition that a predetermined time is lapsed after the previous anchoring condition is satisfied, (III) if said one of the current anchoring conditions is satisfied, a process of generating a specific roof hash value by applying a Merkle tree operation to each of leaf nodes respectively including each of hash values of each of the certificates stored after the previous anchoring condition is satisfied, (IV) one of (IV-1) a process of storing the specific transaction including the specific root hash value in a distributed, database on the blockchain network, and (IV-2) a process of instructing at least one of blockchain nodes in the blockchain network to store the specific transaction in the distributed database, and (V) a process of acquiring a specific transaction ID representing a location of the specific transaction on the distributed database.
 23. The certificate-managing server of claim 22, further comprising processes of: (VI) if a request for verification of the specific certificate including identification information on the specific user is acquired, generating a specific root hash value for comparison by applying the Merkle tree operation to each of leaf nodes respectively including each of hash values for comparison of each of the certificates corresponding to specific root hash identification information, by referring to the specific root hash identification information corresponding to the specific identification information on the specific user, wherein the specific root hash identification information includes information for identifying a specific root hash value for reference which is the specific root hash value generated at the process of (III), (VII) one of (VII-1) retrieving from the distributed database the specific root hash value, as a specific root hash value for reference, included in the specific transaction corresponding to the specific transaction ID, and (VII-2) instructing at least one of the blockchain nodes to retrieve from the distributed database the specific root hash value for reference included in the specific transaction corresponding to the specific transaction ID, and (VIII) confirming a validity of the specific certificate by referring to the specific root hash value for comparison and the specific root hash value for reference.
 24. The certificate-managing server of claim 23, wherein, at the process of (VIII), the processor, if the specific root hash value for reference is determined as different from the specific root hash value for comparison, compares (i) a specific hash value for reference included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root, hash value for reference and (ii) a specific hash value for comparison included in a leaf node, of the specific user, among the leaf nodes corresponding to the specific root hash value for comparison, to thereby confirm the validity of the specific certificate.
 25. The certificate-managing server of claim 23, wherein, at the process of (VIII), the processor, if the specific roof hash value for reference is determined as different from the specific root hash value for comparison, compares (i) each of hash values for reference included in each of the leaf nodes corresponding to the specific root hash value for reference, and (ii) each of hash values for comparison included in each of the leaf nodes corresponding to the specific root hash value for comparison, to thereby determine at least one forged certificate, among the certificates, corresponding to the specific roof hash identification information.
 26. The certificate-managing server of claim 22, wherein, before the process of (III), the processor, if said one of the current anchoring conditions is satisfied, performs (i) one of (i-1) a process of retrieving from the distributed database each of previous root hash values for reference included in each of previous transactions corresponding to each of previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, and (i-2) a process of instructing the at least one of the blockchain nodes on the blockchain network to retrieve from the distributed database each of the previous root hash values for reference included in each of the previous transactions corresponding to each of the previous transaction IDs, by referring to the previous transaction IDs acquired before said one of the current anchoring conditions is satisfied, (ii) a process of acquiring each of previous certificates corresponding to each of the previous root hash values for reference, and a process of generating each of previous root hash values for comparison by applying the Merkle tree operation to each of leaf nodes including each of previous hash values for comparison of said each of the previous certificates, and (iii) a process of comparing said each of the previous root hash values for comparison and said each of the previous root hash values for reference, to thereby confirm a validity of the previous certificates.
 27. The certificate-managing server of claim 22, wherein, at the process of (III), one of the leaf nodes includes a certain previous root hash value created right before said one of the current anchoring conditions is satisfied.
 28. The certificate-managing server of claim 22, wherein, at the process of (iii), the processor manages (i) specific root hash identification information which is information used for identifying the specific root hash value, and (ii) specific node index information which is information on (ii-1) each of locations of each of the leaf nodes including each of the hash values of each of the certificates and (ii-2) each of the hash values of each of the certificates. 